Step 4: Full View

Entities, provisions, decisions, and narrative

Back to Case
Signing and Sealing Plans Not Prepared by Engineer
Step 4 of 5

151

Entities

3

Provisions

1

Precedents

14

Questions

15

Conclusions

Transfer

Transformation
Transfer Resolution transfers obligation/responsibility to another party
The scenario transforms from a single-point sealing model (Engineer A sealing all subordinate work under general direction/supervision) to a distributed sealing model in which the registered engineers who possess direct, detailed knowledge of their own designs assume the sealing obligation themselves. Engineer A is relieved of the improper practice of sealing unreviewed work, and the 'responsible charge' duty is reassigned to the parties actually capable of fulfilling it.
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

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

II.2.a board + analysis Engineers shall undertake assignments only when qualified by education or experience in the specific technical fields involved.
How this applies in the case (showing 3 of 18)
Obligation
Engineer A Seal Cognizance Duty
Engineer must possess competence and understanding before sealing work in that field
Action
Sealing Unregistered Engineers' Plans
Sealing plans outside qualification violates competence requirement
State
Engineer A Qualification Shortfall
This provision requires competence matching the technical field which Engineer A lacks
Obligation (2)
  • Engineer A Seal Cognizance Duty
    Engineer must possess competence and understanding before sealing work in that field
  • Engineer A Responsible Charge Supervision Duty
    Qualification by education or experience underlies the ability to properly supervise and direct the work
Action (2)
  • Sealing Unregistered Engineers' Plans
    Sealing plans outside qualification violates competence requirement
  • Detailed Review Omission
    Failing to review plans risks sealing work outside ones qualification
State (2)
  • Engineer A Qualification Shortfall
    This provision requires competence matching the technical field which Engineer A lacks
  • Unlicensed Staff Preparation Condition
    Preparation by unlicensed staff raises the qualification requirement for the sealing engineer
Constraint (1)
  • Engineer A Work Acceptance Competence Limit
    This provision requires engineers to only undertake assignments within their qualifications matching this constraint.
Principle (1)
  • Competence in Accepting Assignments
    This provision directly requires engineers to accept assignments only within their qualified technical fields
Role (3)
  • Engineer A Chief Engineer
    He must only undertake assignments in fields where he is qualified by education or experience
  • Registered Engineers Subordinate Engineers
    They must only prepare plans in technical fields where they are qualified
  • Graduate Engineers Subordinate Engineers
    They must only prepare plans in technical fields where they are qualified
Event (1)
  • Review Capacity Overload
    Overload situation raises question of whether engineer remains qualified to adequately review the work
Resource (1)
  • BER Case 85-3
    This prior case directly addresses the ethics of accepting work without proper qualifications
Capability (5)
  • Engineer A Supervisory Control
    Engineer A must be qualified to direct and set design requirements for the projects he supervises
  • Registered Engineers Design Competence
    Registered engineers must be qualified by education or experience to prepare the plans they design
  • Graduate Engineers Design Competence
    Graduate engineers must have sufficient competence in the technical fields to prepare plans under supervision
  • Engineer A Technical Advisory
    Engineer A must be qualified to answer technical questions and provide direction on design matters
  • Engineer A Managerial Guidance
    Engineer A must have competence to provide guidance and counsel on technical projects
II.2.b board + analysis Engineers shall not affix their signatures to any plans or documents dealing with subject matter in which they lack competence, nor to any plan or document not prepared under their direction and control.
How this applies in the case (showing 3 of 29)
Obligation
Engineer A Sealing Review Duty
Engineer must review plans in depth before sealing to ensure they were prepared under his direction and control
Action
Sealing Registered Engineers' Plans
Governs whether sealing plans prepared by other registered engineers is proper
State
Seal On Unreviewed Subordinate Plans
Sealing plans not reviewed violates the rule against signing undirected or uncontrolled work
Obligation (3)
  • Engineer A Sealing Review Duty
    Engineer must review plans in depth before sealing to ensure they were prepared under his direction and control
  • Engineer A Responsible Charge Supervision Duty
    Prohibits sealing documents not prepared under the engineer's actual direction and supervision
  • Engineer A Seal Cognizance Duty
    Engineer shall not seal documents in subject matter where he lacks competence
Action (4)
  • Sealing Registered Engineers' Plans
    Governs whether sealing plans prepared by other registered engineers is proper
  • Sealing Unregistered Engineers' Plans
    Prohibits sealing documents not prepared under the sealing engineers direction and control
  • Detailed Review Omission
    Omitting review conflicts with the duty to ensure direction and control over sealed work
  • Ethical Correctness Judgment
    Provision defines the standard used to judge ethical correctness of sealing practices
State (5)
  • Seal On Unreviewed Subordinate Plans
    Sealing plans not reviewed violates the rule against signing undirected or uncontrolled work
  • Belief In Correctness Of Sealing Practice
    The mistaken belief conflicts with the clear prohibition on sealing uncontrolled documents
  • General Direction Supervision Arrangement
    General direction without control does not satisfy the direction and control requirement
  • Unlicensed Staff Preparation Condition
    Plans prepared by unlicensed staff must still be under the engineers direction and control
  • Engineer A Qualification Shortfall
    Lack of competence directly triggers the prohibition on sealing such documents
Constraint (2)
  • Engineer A Seal Without Review
    This provision directly prohibits sealing plans lacking competence or not prepared under direction and control.
  • Engineer A Seal Cognizance Boundary
    This provision establishes the cognizance and competence boundary for affixing signatures and seals.
Principle (4)
  • Understanding and Cognizance Before Sealing
    This provision requires competence and understanding before affixing a seal to documents
  • Responsible Charge in Sealing Plans
    This provision requires plans be prepared under the sealing engineers direction and control
  • Review Adequacy in Chief Engineer Sealing
    This provision implies a need for adequate review to ensure competence in sealed subject matter
  • Responsible Charge in Sealing Delegated Plans
    This provision defines the direction and control standard relevant to delegated plan sealing
Role (3)
  • Engineer A Chief Engineer
    He affixes his seal to plans and must ensure they were prepared under his direction and control and within his competence
  • Registered Engineers Subordinate Engineers
    As registered engineers they are bound not to seal work outside their competence or not under their control
  • Graduate Engineers Subordinate Engineers
    Their work is sealed by another and the provision governs whether such sealing practice is proper
Event (1)
  • Plan Completion
    Signing completed plans not prepared under the engineers direction and control violates this provision
Resource (2)
  • Websters New Collegiate Dictionary
    The dictionary is used to define direction and control as referenced in this provision
  • NCEE Model Law
    The Model Law defines responsible charge which relates to the direction and control requirement
Capability (5)
  • Engineer A Supervisory Control
    Engineer A seals plans only for work prepared under his direction and control
  • Registered Engineers Design Competence
    Engineer A seals plans prepared by registered engineers under his direction, requiring assurance of competence
  • Graduate Engineers Design Competence
    Engineer A seals plans prepared by graduate engineers, raising questions about competence and direct control
  • Engineer A Technical Advisory
    Engineer A's advisory role supports his claim of direction and control over sealed documents
  • Engineer A Managerial Guidance
    Managerial guidance is used to justify that plans are prepared under Engineer A's direction and control
II.2.c board + analysis Engineers may accept assignments and assume responsibility for coordination of an entire project and sign and seal the engineering documents for the entire project, provided that each technical segment is signed and sealed only by the qualified engineers who prepared the segment.
How this applies in the case (showing 3 of 18)
Obligation
Engineer A Segment Sealing Duty
Allows overall project sealing by coordinating engineer while each segment is sealed by the qualified engineer who prepared it
Action
Sealing Registered Engineers' Plans
Allows sealing entire project when segments are signed by qualified engineers who prepared them
State
Review Infeasibility In Large Firm
This provision allows coordination sealing only if each segment is properly reviewed and sealed by qualified engineers
Obligation (1)
  • Engineer A Segment Sealing Duty
    Allows overall project sealing by coordinating engineer while each segment is sealed by the qualified engineer who prepared it
Action (3)
  • Sealing Registered Engineers' Plans
    Allows sealing entire project when segments are signed by qualified engineers who prepared them
  • Supervisory Structure Establishment
    Supports establishing supervisory coordination for sealing entire project documents
  • Board Segment-Sealing Determination
    Provision directly governs the boards determination on segment sealing requirements
State (3)
  • Review Infeasibility In Large Firm
    This provision allows coordination sealing only if each segment is properly reviewed and sealed by qualified engineers
  • General Direction Supervision Arrangement
    Coordination sealing requires actual direction and control not just general supervision
  • Seal On Unreviewed Subordinate Plans
    Unreviewed plans fail the requirement that each segment be properly signed and sealed by the responsible engineer
Constraint (1)
  • Engineer A Segment Seal Exclusivity
    This provision requires each technical segment to be signed and sealed only by the qualified engineer who prepared it.
Principle (2)
  • Responsible Charge in Sealing Plans
    This provision allows sealing an entire project under general coordination with proper segment sealing
  • Responsible Charge in Sealing Delegated Plans
    This provision clarifies conditions under which delegated technical segments may be sealed by the coordinating engineer
Role (3)
  • Engineer A Chief Engineer
    As coordinator he may seal the entire project only if each segment is sealed by the qualified engineer who prepared it
  • Registered Engineers Subordinate Engineers
    They should sign and seal the technical segments they personally prepared
  • Graduate Engineers Subordinate Engineers
    As non-registered engineers they cannot seal their own segments under this provision
Event (1)
  • Plan Completion
    Completed plans must be signed only by the qualified engineer who prepared that segment
Resource (1)
  • NCEE Model Law
    The Model Law definition of responsible charge supports the coordination and sealing rules in this provision
Capability (3)
  • Engineer A Supervisory Control
    Engineer A coordinates the entire project and seals documents as permitted for overall project responsibility
  • Registered Engineers Design Competence
    Qualified registered engineers may sign and seal their own technical segments per this provision
  • Graduate Engineers Design Competence
    Graduate engineers not registered cannot independently seal segments, raising a compliance issue with this provision
Cross-Case Connections
View Extraction
Explicit Board-Cited Precedents 1 Lineage Graph

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

Principle Established:

An engineer may not ethically accept a position or role for which he lacks the requisite qualifications or experience, even if the role is primarily oversight rather than direct preparation of documents.

Citation Context:

Cited to show a prior instance where an engineer lacking qualifications in a field accepted an oversight role, but distinguished because the present case does not involve a lack of qualifications, only the issue of delegation and sealing.

Relevant Excerpts
discussion: "For example, 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... 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 56% Facts Similarity 57% Discussion Similarity 70% Provision Overlap 67% Outcome Alignment 100% Tag Overlap 100%
Shared provisions: II.2.a, II.2.b Same outcome unethical View Synthesis
Component Similarity 51% Facts Similarity 42% Discussion Similarity 55% Provision Overlap 75% Outcome Alignment 100% Tag Overlap 100%
Shared provisions: II.2.a, II.2.b, II.2.c Same outcome unethical View Synthesis
Component Similarity 54% Facts Similarity 67% Discussion Similarity 52% Provision Overlap 75% Outcome Alignment 100% Tag Overlap 60%
Shared provisions: II.2.a, II.2.b, II.2.c Same outcome unethical View Synthesis
Component Similarity 68% Facts Similarity 65% Discussion Similarity 54% Provision Overlap 33% Tag Overlap 100%
Shared provisions: II.2.b View Synthesis
Component Similarity 50% Facts Similarity 48% Discussion Similarity 61% Provision Overlap 25% Outcome Alignment 100% Tag Overlap 33%
Shared provisions: II.2.b Same outcome unethical View Synthesis
Component Similarity 65% Facts Similarity 57% Discussion Similarity 64% Outcome Alignment 100% Tag Overlap 25%
Same outcome unethical View Synthesis
Component Similarity 57% Facts Similarity 48% Discussion Similarity 63% Outcome Alignment 100% Tag Overlap 40%
Same outcome unethical View Synthesis
Component Similarity 61% Facts Similarity 69% Discussion Similarity 60% Outcome Alignment 100% Tag Overlap 25%
Same outcome unethical View Synthesis
Component Similarity 56% Facts Similarity 49% Discussion Similarity 71% Outcome Alignment 100% Tag Overlap 40%
Same outcome unethical View Synthesis
Component Similarity 45% Facts Similarity 30% Discussion Similarity 62% Outcome Alignment 100% Tag Overlap 67%
Same outcome unethical 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.
Resolved by: The board weighed administrative convenience of a single supervisory seal against the individual duty of detailed personal verification, and found the verification duty controlling. (confidence 0.85)
II.2.b. 2 principles 3 facts Conditions Narrative
Implicit (4)

Does Engineer A's model of 'general direction and supervision' actually satisfy the legal and ethical standard of 'responsible charge,' or is it a distinct and lesser form of oversight?

AnalyticalThe Board's finding implies that 'general direction and supervision'—as Engineer A defines it (helping establish concepts, design requirements, and periodically reviewing project status)—is categorically distinct from and insufficient to constitute the 'responsible charge' required for sealing engineering work. Genuine responsible charge requires personal, detailed technical verification of the work product itself, not merely oversight of process, conceptual framing, and availability for consultation on technical questions.
Resolved by: The board weighed Engineer A's characterization of managerial oversight as sufficient against the code's requirement of direct technical control, concluding that process oversight cannot substitute for detailed technical verification. (confidence 0.85)
II.2.b. 3 principles 3 facts Conditions Narrative
AnalyticalRegarding Q101: Engineer A's 'general direction and supervision' model—involving conceptual input, setting design requirements, and periodic status review—does not equate to the legal and ethical standard of 'responsible charge.' Responsible charge requires the sealing engineer to have detailed, personal knowledge of the specific engineering decisions embodied in the plans, not merely oversight of process and personnel. Engineer A's arrangement is a distinct, lesser form of managerial supervision that falls short of the direct technical control implied by affixing one's seal.
Resolved by: The board weighed managerial supervision of personnel and process against the direct technical control required for sealing, concluding the former is a distinct and lesser form of oversight. (confidence 0.80)
II.2.b. 2 principles 3 facts Conditions Narrative

Should the individual registered engineers who actually prepared the plans be required to affix their own seals instead of relying solely on Engineer A's seal?

AnalyticalThe Board's conclusion suggests that the appropriate remedy is not merely restraint by Engineer A but a structural change: the registered engineers who actually prepare plans under his general direction should affix their own seals, since they possess direct, detailed knowledge of the work and are the ones in genuine responsible charge of it. Engineer A's supplementary seal, if used at all, should be confined to matters he has actually reviewed in detail (e.g., overall project coordination under II.2.c.) rather than substituting for the preparer's own sealing obligation.
Resolved by: The board weighed centralized sealing by a single supervisory engineer against distributed sealing by the actual preparers, and favored distributed sealing as more consistent with genuine responsible charge. (confidence 0.80)
II.2.c. 2 principles 3 facts Conditions Narrative
AnalyticalRegarding Q102: The plans should ideally be sealed by the registered engineers who actually prepared them, since they possess the detailed technical knowledge required for responsible charge. Engineer A's practice of sealing on their behalf, while they remain unsealed, effectively substitutes managerial trust for the individualized accountability that licensure and sealing are meant to establish, undermining the traceability of professional responsibility for specific design decisions.
Resolved by: The board weighed the firm's interest in centralized, efficient sealing under a chief engineer against the individualized accountability that licensure is designed to establish, and favored individualized sealing by the actual preparers. (confidence 0.75)
II.2.b. II.2.c. 3 principles 3 facts Conditions Narrative

Does the sheer scale of the firm's project volume represent an organizational failure to allocate adequate review resources, rather than a legitimate excuse for Engineer A's inability to review plans in detail?

AnalyticalThe scale of the firm and the resulting impossibility of detailed review should not be treated as a mitigating circumstance for Engineer A but rather as evidence of an organizational design flaw: the firm has structured its review process in a way that makes ethical sealing practice impossible for a single Chief Engineer, meaning the ethical failure is systemic and points to a need for either more distributed sealing authority (each qualified engineer sealing their own work) or additional layers of licensed reviewers, rather than continued reliance on one individual's seal across an unmanageable volume of projects.
Resolved by: The board weighed the firm's operational scale as a possible excuse against the individual and organizational duty to ensure adequate review, and rejected scale as mitigating, treating it instead as an organizational failure. (confidence 0.80)
II.2.a. 2 principles 3 facts Conditions Narrative

Is there a heightened ethical risk when Engineer A seals plans prepared by non-registered graduate engineers, given that no independently licensed professional has reviewed or taken responsibility for that work before it reaches him?

AnalyticalRegarding Q104: Sealing plans prepared by non-registered graduate engineers presents a heightened ethical risk compared to sealing plans of registered engineers, because in the latter case at least a licensed professional has exercised independent judgment on the work, whereas in the former, Engineer A's seal becomes the sole point of licensed accountability for work that has received no prior independent professional certification. This makes Engineer A's failure to conduct detailed review particularly consequential in the graduate-engineer scenario.
Resolved by: The board weighed the acceptability of relying on a prior layer of licensed judgment (present when preparers are registered) against its complete absence when preparers are unregistered, concluding the latter case carries materially higher ethical risk. (confidence 0.80)
II.2.b. 3 principles 3 facts Conditions Narrative
Principle tension (3)

How should the principle of Responsible Charge in Sealing Plans be balanced against Review Adequacy in Chief Engineer Sealing when the scale of a firm makes detailed personal review of every project practically impossible?

AnalyticalThe Board resolved the tension between Responsible Charge in Sealing Plans and Review Adequacy in Chief Engineer Sealing decisively in favor of the former: organizational scale and workload, however real, cannot dilute the personal, non-delegable duty that sealing entails. Practical infeasibility of detailed review is treated not as a mitigating circumstance but as evidence that the sealing practice itself is structurally unsound, meaning the firm's operational model must yield to the ethical standard rather than the reverse.
Resolved by: The board subordinates review adequacy concerns arising from organizational scale to the non-delegable personal duty of responsible charge, treating infeasibility as disqualifying the practice rather than excusing it. (confidence 0.85)
II.2.b. II.2.c. 2 principles 2 facts Conditions Narrative

Does Engineer A's Competence in Accepting Assignments conflict with his actual capacity to fulfill Understanding and Cognizance Before Sealing, given the number of concurrent projects under his seal?

AnalyticalCompetence in Accepting Assignments and Understanding and Cognizance Before Sealing are shown to be inseparable rather than independently satisfiable: Engineer A's technical qualifications as Chief Engineer do not, by themselves, establish competence to seal a given set of plans if his actual role prevents him from acquiring the specific cognizance those plans require. This reframes 'competence' as project-specific and verification-dependent, not merely a general credential held by virtue of position or experience.
Resolved by: General competence and specific cognizance are treated as jointly necessary rather than substitutable, so a high degree of the former cannot compensate for an absence of the latter. (confidence 0.80)
II.2.a. II.2.b. 2 principles 2 facts Conditions Narrative

How should Responsible Charge in Sealing Delegated Plans be reconciled with a supervisory model based on trust in subordinates' competence rather than direct, detailed verification of their work?

AnalyticalResponsible Charge in Sealing Delegated Plans cannot be satisfied by a supervisory model grounded in interpersonal trust and general direction alone; the Board implicitly prioritizes verified, documented engineering judgment over confidence in subordinates' competence, however well-founded. Trust in staff may justify delegation of design work, but it cannot substitute for the sealing engineer's own detailed understanding, revealing that 'responsible charge' is an epistemic standard (what the sealer actually knows) rather than a managerial or relational one (whom the sealer trusts).
Resolved by: Interpersonal trust in subordinates is weighed against the need for the sealer's own verified understanding, with the board prioritizing documented personal knowledge over relational confidence as the basis for responsible charge. (confidence 0.80)
II.2.b. II.2.c. 2 principles 2 facts Conditions Narrative
Theoretical (3)

From a deontological perspective, did Engineer A fulfill his duty to personally verify and understand the engineering work before affixing his professional seal, regardless of his confidence in subordinates?

AnalyticalRegarding Q301 (deontological perspective): Engineer A did not fulfill his duty to personally verify and understand the engineering work before sealing it. A deontological reading of the sealing requirement treats it as a categorical duty attached to the individual engineer's act of certification, not a delegable managerial function; confidence in subordinates' competence, however well-founded, cannot substitute for the engineer's own direct cognizance of the work he certifies.
Resolved by: The board treated the duty to personally verify work as a non-delegable categorical obligation that outweighs any managerial rationale for trusting subordinates without direct review. (confidence 0.80)
II.2.b. 2 principles 3 facts Conditions Narrative

From a consequentialist perspective, does the fact that no harm has yet resulted from Engineer A's practice of sealing unreviewed plans justify continuing that practice given the firm's scale and workload?

AnalyticalRegarding Q302 (consequentialist perspective): The absence of harm to date does not justify continuing the practice, because consequentialist analysis must account for probabilistic risk, not just realized outcomes. Given the volume of concurrent projects and the admitted impossibility of detailed review, the expected value calculation favors changing the practice, since a single undetected design flaw sealed under Engineer A's name could produce serious harm, and the current practice systematically increases that risk across many projects simultaneously.
Resolved by: The board weighed the absence of realized harm against the probabilistic risk created by systemic lack of review across many projects, concluding that expected-value risk outweighs the clean track record. (confidence 0.75)
II.2.b. 2 principles 3 facts Conditions Narrative

Did Engineer A act with professional integrity, in the virtue-ethical sense, by presenting his seal as a guarantee of competent oversight when he candidly admits he cannot conduct detailed review of the underlying work?

AnalyticalRegarding Q303 (virtue ethics perspective): Engineer A's candid admission that he cannot conduct detailed review, combined with his continued practice of sealing, reflects a lack of full professional integrity, because the seal is publicly understood as a representation of the sealing engineer's own diligence and competent oversight. Continuing the practice despite acknowledging this gap suggests a rationalization of convenience rather than a virtuous engineer's honest alignment of representation with actual conduct.
Resolved by: The board weighed the public representational meaning of the seal against Engineer A's own admitted practice, finding the mismatch between representation and conduct indicative of rationalized convenience rather than virtuous integrity. (confidence 0.75)
II.2.b. 2 principles 3 facts Conditions Narrative
Counterfactual (3)

If the registered engineers working under Engineer A's general direction had affixed their own seals to the plans they prepared, would the Board still have found Engineer A's practice of also sealing those plans unethical?

AnalyticalRegarding Q401: Even if the registered engineers who prepared the plans had affixed their own seals, the Board would likely still have found it problematic for Engineer A to additionally seal plans he had not detailed-reviewed, because dual sealing without independent verification would still misrepresent Engineer A's actual level of engagement with the specific design, though the ethical severity would likely be reduced since at least one qualified, accountable seal would already exist on the document.
Resolved by: The obligation of personal cognizance before sealing is weighed as prior to and independent of whether another qualified seal already exists, though the presence of an accountable seal reduces the practical harm at stake. (confidence 0.75)
II.2.b. 2 principles 2 facts Conditions Narrative

If the graduate engineers whose plans Engineer A sealed had been registered professional engineers rather than non-registered, would the Board's conclusion about the unethical nature of Engineer A's sealing practice still apply in the same way?

Also discussed in: C203

If the firm's size and project volume had been small enough that Engineer A could feasibly conduct a detailed review of every design, would the Board still have concluded that his sealing practice was unethical?

AnalyticalRegarding Q403: The Board's conclusion is framed around the general ethical principle that sealing requires detailed review, not around firm size specifically; thus even if Engineer A's firm were small enough to make full review feasible, the same underlying obligation would apply, and the case would likely have turned on whether Engineer A actually performed that feasible review rather than on the current facts, which establish that he did not and could not.
Resolved by: The general duty to review before sealing is treated as fixed regardless of firm size, so the balancing collapses into a factual question of whether review was actually performed rather than a principled tradeoff between feasibility and duty. (confidence 0.75)
II.2.b. 2 principles 2 facts Conditions Narrative
Decisions & Arguments (5)
View Extraction

Should Engineer A seal plans based on general direction and supervision of subordinates, or conduct a detailed personal review of the specific engineering content before sealing?

Options considered:
O1 Continue sealing plans based on establishing concepts, setting design requirements, and periodic status checks without line-by-line technical review.
O2 Personally review the specific engineering content of each plan in sufficient depth to take responsibility for its correctness before affixing his seal. Board's choice
O3 Perform detailed review only of critical or safety-significant design elements while relying on general supervision for routine portions of the work.
Argument structure (Toulmin):
Grounds

Engineer A oversees a large volume of concurrent projects, reviews plans only generally rather than in detail, and some plans are prepared by non-registered graduate engineers before reaching him.

Warrant

An engineer must sign and seal only work in which he possesses direct understanding and cognizance, established through personal review of the design as it develops; general managerial direction and confidence in subordinates does not substitute for this personal verification.

Rebuttal

This warrant would not apply if the preparing engineer is independently registered and affixes his own seal to the segment he prepared, transferring the cognizance requirement to that engineer instead.

Engineer A Sealing Review Duty

Should Engineer A alone seal all plans produced under his direction, or should the registered engineers who prepared each segment affix their own seals to that segment?

Options considered:
O1 Maintain the current practice in which Engineer A affixes his seal to all plans produced under his general direction, regardless of who prepared them.
O2 Require each registered engineer who prepared a technical segment to affix his own seal, with Engineer A sealing only overall coordination matters he has personally reviewed. Board's choice
O3 Have both the preparing engineer and Engineer A seal the same segment, layering supervisory sealing atop preparer sealing without eliminating either.
Argument structure (Toulmin):
Grounds

Registered engineers working under Engineer A's general direction prepare specific technical segments of plans, and Engineer A currently affixes his own seal to that work without the preparers also sealing it.

Warrant

Each technical segment of a project shall be signed and sealed only by the qualified engineer who prepared it, since that engineer possesses the direct, detailed knowledge required for responsible charge of that segment.

Rebuttal

This claim would not apply if the preparer is not independently registered, in which case no substitute seal exists and Engineer A's own detailed review becomes the sole available point of licensed accountability.

Engineer A Segment Sealing Duty

Should Engineer A seal plans prepared by non-registered graduate engineers based on general supervision, or require direct personal supervision or an intermediate registered review before sealing that work?

Options considered:
O1 Continue sealing plans prepared by non-registered graduate engineers based on general oversight of the firm's design process, without detailed personal review.
O2 Exercise direct, hands-on supervision and detailed technical review of all work produced by non-registered graduate engineers before sealing it. Board's choice
O3 Require an independently registered engineer to review and countersign graduate engineers' work before it reaches Engineer A for final sealing.
Argument structure (Toulmin):
Grounds

Some plans sealed by Engineer A are prepared by non-registered graduate engineers, and Engineer A does not review this work in detail before sealing.

Warrant

An engineer may sign and seal documents only for that in which he possesses genuine understanding and cognizance, and this cognizance requires direct control and personal supervision, which is especially necessary where no independently licensed engineer has already exercised professional judgment on the work.

Rebuttal

This heightened duty would be less acute if an independently registered engineer had already reviewed and taken partial responsibility for the graduate engineer's work before it reached Engineer A.

Engineer A Seal Cognizance Duty

Should Engineer A continue sealing plans at a volume too large for detailed personal review, or restructure the firm's review process by distributing sealing authority or limiting project intake?

Options considered:
O1 Continue accepting the current project volume and have Engineer A seal all plans under the existing general-supervision arrangement.
O2 Redesign the firm's process so that qualified preparers seal their own segments and additional licensed reviewers are added to restore individualized, detailed review. Board's choice
O3 Reduce the number of concurrent projects the firm accepts so that Engineer A can feasibly conduct detailed review of every plan he seals.
Argument structure (Toulmin):
Grounds

Engineer A's firm handles a project volume that leaves him unable to review each plan in detail, yet he continues to seal all of them under the existing supervisory structure.

Warrant

An engineer must accept and seal work only in a manner consistent with actually possessing the qualifications and capacity for genuine cognizance of that work; organizational scale that structurally prevents this obligation from being met constitutes a design flaw, not an excuse.

Rebuttal

This claim would not apply if Engineer A lacked any authority to demand additional reviewers or limit intake, in which case responsibility would shift toward firm management rather than Engineer A individually.

Engineer A Responsible Charge Supervision Duty

Should Engineer A continue his current sealing practice because no harm has yet resulted, or proactively change the practice given the accumulated risk across many concurrent projects?

Options considered:
O1 Maintain the current sealing practice on the grounds that it has not yet produced any known design failure or harm.
O2 Change the sealing practice now, based on the accumulated probabilistic risk across many concurrent projects, rather than waiting for a failure to occur. Board's choice
O3 Keep the current practice in place while instituting periodic risk audits, changing course only if warning signs of inadequate review emerge.
Argument structure (Toulmin):
Grounds

Engineer A has sealed numerous plans without detailed review across many concurrent projects, and no design failure has occurred to date under this practice.

Warrant

Engineers must hold paramount the safety of the public, which requires evaluating expected risk across all sealed work rather than waiting for a realized failure before correcting an unsound practice.

Rebuttal

This claim would not apply if the volume of concurrent projects were low enough that the probability of an undetected design flaw was negligible, making continued reliance on general supervision a reasonable risk judgment.

Engineer A Sealing Review Duty
Event Timeline (8)
8 sequenced 6 actions 2 events
Case timeline
Engineer A hires engineers in whose abilities he places confidence and establishes an ongoing practice of general direction and supervision, helping to set design concepts and requirements, reviewing design elements as work progresses, and answering technical questions when consulted.
Causal-normative reasoning(confidence 0.70)
A2, though guided by the Responsible Charge standard and not itself a violation, is the upstream act that produces Plan Completion, so its adequacy or inadequacy in exercising real oversight directly determines whether the later sealing actions (A1 and A4) can legitimately satisfy or will instead breach sealing obligations.
State changes (1)
  • began: General Direction Supervision Arrangement
Due to the size of the organization and the large number of concurrent projects, it became impossible for Engineer A to give a detailed review or check of each design before sealing. This condition arose from the firm's scale and workload rather than from a deliberate intervention.
State changes (2)
  • began: General Direction Supervision Arrangement
  • began: Review Infeasibility In Large Firm
Plans prepared by registered engineers and by non-registered graduate engineers under Engineer A's general direction become complete and ready for sealing, with the preparing registered engineers not affixing their own seals. This recurring completion of unsealed plans is the occurrence that presents Engineer A with documents to seal.
Given the size of the organization and the volume of concurrent projects, Engineer A chooses not to give a detailed review or check of the designs before affixing his seal.
Violates (1)
  • Sign and Seal Only Work Prepared Under Direction and Control (II.2.b)
Causal-normative reasoning(confidence 0.80)
A5 violates the sign-and-seal obligation because skipping detailed review, caused by Review Capacity Overload, means the Chief Engineer sealed work without the verification the rule demands, and this omission directly shaped the Ethical Correctness Judgment that followed, linking capacity failure to a compromised ethical evaluation.
State changes (1)
  • began: Seal On Unreviewed Subordinate Plans
Engineer A affixes his seal to plans prepared by registered engineers working under his general direction, engineers who do not affix their own seals to those plans.
Violates (2)
  • Sign and Seal Only Work Prepared Under Direction and Control (II.2.b)
  • Each Technical Segment Sealed by the Qualified Engineer Who Prepared It (II.2.c)
Engineer A also seals plans prepared by non-registered graduate engineers working under his general supervision, without direct control and personal supervision of that work.
Violates (2)
  • Sign and Seal Only Work Prepared Under Direction and Control (II.2.b)
  • Direct Control and Personal Supervision of Unlicensed Engineers' Work
Engineer A judges his sealing practice to be ethically and legally correct, grounding that conclusion in his confidence in the ability of the engineers he hired and supervises.
Causal-normative reasoning(confidence 0.60)
A3 has no fulfills or violates edges itself, but as the judgment triggered by the Detailed Review Omission it represents the engineer's ethical self-assessment that determined whether the omission and subsequent sealing practices would be treated as acceptable, making it a normative pivot point rather than a directly rule-bound act.
The Board determines that each technical segment must be signed and sealed only by the qualified engineers who prepared it, and that work by non-registered engineers must be performed under the direct control and personal supervision of registered engineers who would seal the documents.
Fulfills (2)
  • Each Technical Segment Sealed by the Qualified Engineer Who Prepared It (II.2.c)
  • Direct Control and Personal Supervision of Unlicensed Engineers' Work
Causal-normative reasoning(confidence 0.80)
Because Engineer A's sealing of unregistered engineers' plans created the very situation the Board had to evaluate, the Board's determination that each segment must be sealed by the qualified engineer who prepared it, and that unlicensed engineers' work requires direct personal supervision, directly addresses and condemns the causal chain from supervisory structure establishment through plan completion to sealing unregistered engineers' plans, reinforcing that responsible charge cannot be satisfied merely by overseeing a large operation but requires genuine engineering judgment and control over what is sealed.
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 handling numerous projects simultaneously. Registered engineers working under your general direction prepare plans for various projects, but many of them do not affix their own seals to their completed work. You also oversee non-registered graduate engineers whose designs sometimes come to you for sealing as well. Your involvement typically consists of setting the initial concept, establishing design requirements, and reviewing overall project status as work progresses, along with fielding technical questions from your staff. Given the volume of projects moving through the firm at any given time, you find it impossible to conduct a detailed review or check of each design before applying your seal, and you have relied instead on your confidence in the engineers you have hired and supervise. You now face a series of decisions about how to handle the sealing of these plans going forward.

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

Engineer A carries a duty to seal the segments of work for which he is organizationally responsible as chief engineer, but the competence limit constraint bars him from accepting or certifying work that falls outside his own area of technical expertise. When graduate or registered engineers produce specialized technical segments beyond Engineer A's personal competence, he faces a conflict between the institutional expectation that he seal all segments under his charge and the ethical requirement that he not certify work he is not qualified to evaluate.

As chief engineer, Engineer A has a duty to supervise the entire project in responsible charge, which creates pressure to seal the complete body of work produced by subordinate registered and graduate engineers. However, the constraint on segment seal exclusivity limits him to sealing only those segments he personally directed or reviewed in sufficient depth. This creates tension when subordinates complete technical segments independently under general rather than direct supervision, leaving Engineer A caught between organizational expectations of comprehensive sealing authority and the ethical limit on sealing work he did not personally verify in detail.

Engineer A is obligated to conduct a thorough review before affixing his seal to any set of documents, yet the cognizance boundary constrains him to only certify matters within his direct personal knowledge and involvement. On a large multi-engineer project this creates tension because a review sufficient to satisfy the duty may still fall short of the deep, hands-on cognizance the boundary demands, especially for specialized segments handled by other registered engineers. Engineer A must decide how much review is enough to responsibly claim cognizance without overstepping into territory he cannot genuinely vouch for.

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

Guided by: Responsible Charge in Sealing Plans, Review Adequacy in Chief Engineer Sealing, Responsible Charge in Sealing Delegated Plans

Engineer A carries a duty to seal the segments of work for which he is organizationally responsible as chief engineer, but the competence limit constraint bars him from accepting or certifying work that falls outside his own area of technical expertise. When graduate or registered engineers produce specialized technical segments beyond Engineer A's personal competence, he faces a conflict between the institutional expectation that he seal all segments under his charge and the ethical requirement that he not certify work he is not qualified to evaluate.

As chief engineer, Engineer A has a duty to supervise the entire project in responsible charge, which creates pressure to seal the complete body of work produced by subordinate registered and graduate engineers. However, the constraint on segment seal exclusivity limits him to sealing only those segments he personally directed or reviewed in sufficient depth. This creates tension when subordinates complete technical segments independently under general rather than direct supervision, leaving Engineer A caught between organizational expectations of comprehensive sealing authority and the ethical limit on sealing work he did not personally verify in detail.

Engineer A carries a duty to seal the segments of work for which he is organizationally responsible as chief engineer, but the competence limit constraint bars him from accepting or certifying work that falls outside his own area of technical expertise. When graduate or registered engineers produce specialized technical segments beyond Engineer A's personal competence, he faces a conflict between the institutional expectation that he seal all segments under his charge and the ethical requirement that he not certify work he is not qualified to evaluate.

As chief engineer, Engineer A has a duty to supervise the entire project in responsible charge, which creates pressure to seal the complete body of work produced by subordinate registered and graduate engineers. However, the constraint on segment seal exclusivity limits him to sealing only those segments he personally directed or reviewed in sufficient depth. This creates tension when subordinates complete technical segments independently under general rather than direct supervision, leaving Engineer A caught between organizational expectations of comprehensive sealing authority and the ethical limit on sealing work he did not personally verify in detail.

Engineer A is obligated to conduct a thorough review before affixing his seal to any set of documents, yet the cognizance boundary constrains him to only certify matters within his direct personal knowledge and involvement. On a large multi-engineer project this creates tension because a review sufficient to satisfy the duty may still fall short of the deep, hands-on cognizance the boundary demands, especially for specialized segments handled by other registered engineers. Engineer A must decide how much review is enough to responsibly claim cognizance without overstepping into territory he cannot genuinely vouch for.

Engineer A carries a duty to seal the segments of work for which he is organizationally responsible as chief engineer, but the competence limit constraint bars him from accepting or certifying work that falls outside his own area of technical expertise. When graduate or registered engineers produce specialized technical segments beyond Engineer A's personal competence, he faces a conflict between the institutional expectation that he seal all segments under his charge and the ethical requirement that he not certify work he is not qualified to evaluate.

As chief engineer, Engineer A has a duty to supervise the entire project in responsible charge, which creates pressure to seal the complete body of work produced by subordinate registered and graduate engineers. However, the constraint on segment seal exclusivity limits him to sealing only those segments he personally directed or reviewed in sufficient depth. This creates tension when subordinates complete technical segments independently under general rather than direct supervision, leaving Engineer A caught between organizational expectations of comprehensive sealing authority and the ethical limit on sealing work he did not personally verify in detail.

The Board’s deliberation

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

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.
Opening States (6)
Seal On Unreviewed Subordinate Plans Review Infeasibility In Large Firm Belief In Correctness Of Sealing Practice General Direction Supervision Arrangement Engineer A Qualification Shortfall Unlicensed Staff Preparation Condition
Summary
  • A professional seal certifies personal knowledge and direct involvement, not organizational title or supervisory rank.
  • Chief engineers cannot rely on general oversight of a project to justify sealing segments prepared and reviewed by other engineers without their own detailed involvement.
  • The duty to seal only what one has personally prepared or thoroughly reviewed overrides institutional expectations that a single senior engineer certify an entire multi engineer project.

© Licensed under the GNU GPL v3