Step 4: Review

Engineers shall undertake assignments only when qualified by education or experience in the specific technical fields involved.

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.

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.

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.

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.

The 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.

The 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.

The 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.

Regarding 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.

Regarding 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.

Regarding 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.

Regarding 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.

Regarding 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.

Regarding 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.

Regarding 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.

Regarding 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.

The 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.

Competence 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.

Responsible 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).

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

A1 violates the sign-and-seal and per-segment sealing requirements because sealing plans completed under the supervisory structure without ensuring each registered engineer's segment was properly reviewed and sealed by that engineer undermines the accountability the seal is meant to certify, even though the underlying work came from Plan Completion.

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.

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.

A4 is the most serious violation because sealing unregistered engineers' plans breaches both the general sign-and-seal duty and the specific requirement for direct control and personal supervision of unlicensed engineers, and this same act is what triggers the Board's formal Segment-Sealing Determination, showing how the violation's downstream consequence is institutional scrutiny.

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.

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.

The question arises because a large firm's practical need for a single chief engineer to seal many plans collides with the Code's requirement that sealing reflect direct, detailed personal knowledge of the work, creating uncertainty over whether supervisory oversight can substitute for individual review.

The question arises because the practical impossibility of individually reviewing all plans in a large firm (Review Capacity Overload, Review Infeasibility In Large Firm) forces Engineer A to rely on general direction and supervision, creating ambiguity about whether this managerial arrangement legally and ethically equates to the more demanding standard of responsible charge implied by sealing.

The question emerges because a large firm's practical need for efficient sealing conflicts with the ethical requirement that a sealing engineer be in genuine responsible charge of what he certifies, creating ambiguity about whether the chief engineer's oversight suffices or whether each preparing engineer must independently seal his own work.

The question arises because the same fact, an overwhelming project volume causing unreviewed sealing, can be read either as a mitigating structural circumstance created by the employer or as an aggravating condition Engineer A should have refused to work under, leaving the locus of ethical responsibility contested.

The question arises because sealing unreviewed work from unlicensed subordinates sits at the boundary between acceptable delegated responsible charge and an ethically risky rubber stamp, and the Code's language on direction and control does not clearly resolve which side of that boundary applies when no independent licensed check exists.

The question arises because Review Capacity Overload from firm scale forces a choice between two legitimate but incompatible readings of what responsible charge requires, one procedural (structural supervision) and one substantive (individual review), and the Code does not specify which controls when firm size makes the substantive reading impractical.

The question arises because Engineer A's belief in the correctness of his sealing practice rests on a supervisory structure that may satisfy competence in the abstract but fails the more demanding requirement of case by case understanding before sealing, especially given his large firm's high volume of projects.

The question arises because a large firm's practical need to delegate plan preparation collides with the Code's expectation that a sealing engineer maintain direct control, and no single definition of direction and control resolves how much delegation is permissible.

The question arises because the firm's scale made literal personal review of every plan practically impossible, forcing a choice between a strict deontological reading of sealing duty and a more permissive supervisory interpretation, leaving the ethical status of Engineer A's practice contested.

The question arises because the firm's large scale and workload created a real world scenario where no harm has occurred despite Engineer A sealing plans he could not personally review, forcing a clash between outcome based and duty based ethical reasoning about whether current safety is sufficient justification.

The question arises because the same facts, high volume sealing paired with candid admission of no detailed review, can be read either as a violation of the sealing warrant or as a permissible exercise of managerial responsible charge, leaving the virtue-ethical characterization of integrity unsettled.

The question arises because the Board's finding rested on Engineer A sealing work without adequate personal review, but it left ambiguous whether the impropriety stemmed from the lack of review itself or from displacing the registered engineers' own sealing authority, creating uncertainty about which warrant truly drove the unethical determination.

This question arises because the case explicitly distinguishes registered from non-registered subordinates in defining Engineer A's duties, so altering that fact changes which warrant (responsible charge versus direct control of unlicensed work) governs the ethical analysis and thus whether the same unethical conclusion follows.

The question emerges because the Board's judgment rested on facts about firm size and review infeasibility, and it is unclear whether those facts were the operative warrant condition or merely contextual, so altering them counterfactually tests whether the ethical conclusion depends on feasibility or on the sealing practice itself.

Given that Engineer A admits his review is general rather than detailed and that some plans pass through unlicensed preparers, the board concluded that sealing under these conditions is unethical because the seal represents a personal verification he did not perform.

Because Engineer A's own account described only high-level, process-oriented supervision, the board concluded that this falls short of the responsible charge standard, which demands personal technical knowledge of the work being sealed.

Because the registered subordinate engineers possess the detailed knowledge Engineer A lacks, the board concluded that they, not Engineer A, should seal the plans they prepared, reserving Engineer A's seal for matters of overall coordination he has actually reviewed.

Given that the firm's size makes detailed review by Engineer A alone impossible, the board concluded that this reflects a structural design flaw in the firm's review process rather than a valid excuse for continuing the practice.

Because Engineer A's described role centers on managerial direction rather than technical verification of the plans themselves, the board concluded his practice constitutes a lesser form of oversight that does not satisfy responsible charge.

Given that registered engineers with direct technical knowledge prepared the plans while Engineer A only supervised generally, the board concluded that sealing responsibility should ideally rest with those preparers, since Engineer A's seal in this arrangement substitutes trust for the traceable, individualized accountability licensure requires.

Because the graduate engineers were not registered and no licensed professional had reviewed their work before it reached Engineer A, the board concluded that his sealing without detailed review was especially consequential in this scenario, since his seal alone bore the entire weight of licensed accountability.

Because Engineer A sealed plans based on confidence in his subordinates rather than his own direct cognizance of the work, the board concluded from a deontological standpoint that he failed the categorical duty of personal verification attached to the act of sealing.

Given the admitted impossibility of detailed review across a high volume of concurrent projects, the board concluded that the absence of harm so far does not justify continuing the practice, because consequentialist reasoning must weigh the elevated probability of an undetected flaw, not merely the outcomes realized to date.

Because Engineer A openly acknowledged he could not review the work in detail yet kept sealing it as though he had exercised competent oversight, the board concluded this reflected a lack of full professional integrity, since the seal's public meaning diverged from his actual practice.

Given that the underlying fact of no detailed review by Engineer A does not change merely because subordinates also seal their own work, the board reasons that the ethical problem of misrepresented engagement would persist, though the presence of an independently accountable seal would lessen the real-world consequences of that misrepresentation.

Since the board's reasoning centers on the general obligation to review rather than on firm size as such, the board indicates that a small-firm version of Engineer A would only escape criticism if he actually exercised the feasible review, which the current facts show did not occur.

Given that Engineer A's firm size made individualized detailed review practically impossible while he continued sealing every plan, the board concludes that this scale cannot excuse or dilute the personal duty attached to sealing, so the firm's operational model, not the ethical standard, must change.

Because Engineer A's title and experience as Chief Engineer did not translate into actual detailed knowledge of the specific plans given his role's structural limits, the board treats competence as necessarily project-specific and concludes that general qualification alone cannot satisfy the cognizance requirement.

Given that Engineer A's supervisory arrangement rested on confidence in his subordinates' competence rather than his own detailed engagement with their work, the board concludes that responsible charge demands the sealer's own epistemic grounding, which trust alone, however well-founded, cannot supply.

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?

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?

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?

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?

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?