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.

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.

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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 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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

By accepting the Chief Engineer role without ensuring competence across all technical segments supervised - analogous to Case 85-3's chemical engineer accepting a surveyor role - Engineer A violates the competence prerequisite obligation while nominally assuming professional accountability for directed work.

Institutionalizing a standard of general supervision - conceptual direction and consultative input without detailed design verification - directly violates the responsible charge requirement that direction and control must be substantive and complete, not merely managerial or advisory.

When Engineer A seals plans prepared by registered engineer subordinates without those engineers affixing their own seals, the technical segment attribution obligation is violated because the qualified preparer's professional identity is obscured and Engineer A cannot certify genuine responsible charge over work reviewed only superficially.

Sealing plans prepared by non-registered graduate engineers without exercising direct control and personal supervision - and substituting confidence in subordinate competence for actual verification - represents the most serious violation because non-registered engineers cannot independently seal documents and Engineer A's seal is the sole professional accountability mechanism for that work entering the public record.

Consciously omitting detailed design review - whether rationalized by organizational scale or trust in subordinate competence - is the root ethical failure that renders every subsequent seal affixation a false professional certification, violating the core responsible charge standard that requires active, substantive engagement with the work being sealed.

This foundational question emerged because Engineer A's institutionalized practice of sealing without detailed review created a direct collision between the managerial model of responsible charge and the certification model embedded in the seal obligation. The question could not be avoided once the data showed that plans entered the public record bearing Engineer A's seal without his substantive engagement with their technical content.

This question emerged because the data revealed that Engineer A's firm employed both registered and non-registered subordinates under an identical supervisory model, forcing the analysis to confront whether the ethical code's differentiated language for non-registered work creates separate obligations or a unified standard. The question became unavoidable once it was recognized that relieving registered engineers of their own sealing authority while also sealing non-registered work under general supervision implicated two distinct warrant structures simultaneously.

This question emerged because the data showed that the impossibility of adequate review was not Engineer A's personal failure but a structural feature of the firm's operational design, creating tension between the individual-accountability model embedded in sealing obligations and the systemic causation model that locates ethical responsibility at the organizational level. The question could not be resolved by the foundational analysis alone because finding Engineer A solely responsible without examining the firm's role would leave the structural cause of the violation unaddressed.

This question emerged because the ethics violation determination left open what Engineer A must actually do to come into compliance, and the data showing that registered subordinates were capable of sealing their own work but were institutionally prevented from doing so pointed toward an affirmative restructuring obligation rather than mere abstention. The question arose from the gap between identifying what Engineer A must stop doing and specifying what he must affirmatively do to restore sealing integrity.

This question emerged because the data showed that non-registered graduate engineers, unlike their registered counterparts, have no independent professional obligation or licensure-based accountability to the public, meaning that Engineer A's seal was the only professional certification standing between their unverified work and public reliance. The question arose from the recognition that the ethical analysis of sealing without review may need to be calibrated to the professional standing of the preparer, not merely the adequacy of the supervisor's review process.

This question arose because the NSPE Board's own definitional work on 'direction and control' - the Responsible Charge Standard Clarification state - left open whether managerial-level engagement satisfies responsible charge, creating a normative gap that Engineer A's large-firm supervisory practice directly exposed. The question crystallizes at the boundary where two internally coherent but mutually incompatible standards both claim jurisdiction over the same act of sealing, and neither the NCEE Model Law definition nor the Code provisions resolve which standard governs when organizational scale structurally prevents the more demanding standard from being met.

This question emerged because the firm's practice of having Engineer A seal plans prepared by registered subordinates without those subordinates affixing their own seals created a structural ambiguity: the Non-Substitution Principle treats Engineer A's seal as a personal certification requiring personal knowledge, while the Technical Segment principle treats the registered subordinate's preparation as itself a form of professional accountability that the sealing system should recognize. The tension is irreducible because both principles are grounded in the same underlying value - professional accountability - but locate that accountability in different actors for the same document.

This question arose because the Case 85-3 analogy, when applied to Engineer A's situation, generates a recursive ethical problem: if accepting a role that generates obligations one cannot fulfill is itself the violation, then the chief engineer role in a large firm may be structurally incompatible with the sealing obligations it creates, making the ethical question one of role acceptance rather than supervisory practice. The question is philosophically significant because it shifts the locus of ethical responsibility from the moment of sealing to the prior moment of role acceptance, and the Case 85-3 analogy's cross-domain application is contested precisely because the competence deficit in Engineer A's case is organizational rather than technical.

This question emerged because Section II.2.c's express permission for a coordinating engineer to accept project-wide responsibility creates an internal Code tension: if the seal always means the same thing (personal judgment certification), then the coordination permission is either redundant or impossible to fulfill honestly at scale; but if the coordination permission implies a different seal standard, then the Code itself authorizes a form of sealing that the Seal and Signature Certification principle condemns. The question is structurally generated by the Code's own multi-provision architecture and cannot be resolved without a principled account of how II.2.a, II.2.b, and II.2.c interact.

This question arose because the deontological framing of the seal as a categorical, non-delegable act of personal certification creates an analytically prior question that the other questions presuppose: if the seal is categorical by definition, then all debates about what level of review is 'sufficient' are beside the point, and Engineer A's breach is established the moment he seals without personal knowledge. The question is philosophically necessary because it tests whether the ethical analysis of Engineer A's conduct is fundamentally deontological - in which case the outcome and the quality of subordinates are irrelevant - or whether it is a more contextual inquiry into what responsible charge requires given organizational role and scale.

This question arose because Engineer A's sealing practice created a measurable gap between the formal responsible charge standard and actual review depth, forcing a consequentialist accounting of whether the aggregate public-safety risk generated by that gap is offset by the organizational productivity enabled by the large-firm model. The question could not be resolved by code text alone because consequentialism requires empirical harm-benefit comparison that the deontological code provisions do not supply.

This question emerged because Engineer A's rationalization - that confidence in subordinates satisfies responsible charge - directly contests the virtue-ethics account of what professional integrity demands, creating a dispute about whether the virtuous engineer's obligation is agent-relative (internal character) or role-relative (structural accountability). The question could not be dissolved by appealing to outcomes because virtue ethics evaluates the character of the disposition, not merely its consequences.

This question arose because the simultaneous application of three code provisions to a single sealing act created interpretive ambiguity about whether their combined force is additive (each independently violated) or constitutive (together defining a unified duty whose breach is categorical). The deontological framing sharpened the question by insisting that the ethical violation is located at role-acceptance rather than at any particular downstream harm, a claim that requires the integrated-reading warrant to bear the full argumentative weight.

This question arose because the existing sealing practice created a structural mismatch between who prepared the work and who sealed it, prompting the counterfactual inquiry into whether redistributing sealing authority to qualified preparers would dissolve the responsible charge problem. The question could not be answered by the code text alone because it required determining whether responsible charge is a property of individual document segments or of the integrated project, a distinction the code provisions leave ambiguous.

This question arose because the non-registered graduate engineers' inability to independently seal their own work created an irreducible dependency on Engineer A's seal, forcing the question of whether the direct-supervision prerequisite for that seal is structurally satisfiable at large-firm scale. The question could not be resolved by analogy to registered-subordinate sealing because the absence of licensure removes the distributed-accountability mechanism that makes segment-level sealing a viable alternative, leaving organizational scale and direct supervision in direct structural conflict.

This question emerged because the Board's ethics violation determination against Engineer A created a logical gap: if the sealing practice was ethically impermissible from the outset, then the role as structured was itself the source of the violation, which activates the Case 85-3 warrant that role acceptance under conditions of foreseeable incapacity is independently unethical. The question forces a structural counterfactual - would refusal have produced a better institutional outcome - precisely because the Board condemned the practice without addressing whether the role configuration itself was the root ethical failure.

This question emerged because the Board's condemnation of Engineer A's general supervision practice left open the critical operational question of what a compliant alternative would actually look like in a large engineering organization, creating a gap between the ethical standard as declared and the standard as implementable. The mandatory checkpoint proposal is a direct attempt to construct the minimum viable compliant practice, and the question's deeper implication - whether the Board's standard is workable at organizational scale - surfaces because if no feasible checkpoint system can satisfy responsible charge, the standard effectively prohibits the large-firm chief engineer sealing model entirely, a conclusion the Board did not explicitly reach.

The board concluded that the engineering firm bears independent, non-trivial ethical responsibility because it actively constructed the supervisory architecture that made responsible charge review structurally impossible, and a complete ethical analysis cannot treat the firm as a passive backdrop when its operational decisions systematically undermine the public safety protections that licensure law and the NSPE Code are designed to provide.

The board concluded that it is unethical for Engineer A to seal plans he has not personally prepared or checked and reviewed in detail, because the seal constitutes a substantive certification of personal knowledge and judgment that cannot be delegated to or replaced by trust in subordinates, regardless of their actual competence.

The board concluded that Engineer A committed an antecedent and ongoing ethical breach by accepting and retaining a chief engineer sealing role whose organizational conditions made the discharge of responsible charge impossible, drawing on the BER Case 85-3 analogy to establish that the ethical violation is not merely episodic with each unsealed plan but structural and continuous, requiring Engineer A to have either restructured the firm's model or relinquished the sealing authority.

The board concluded that Engineer A's practice of sealing plans prepared by non-registered graduate engineers under only general supervision constitutes a categorically more serious and separately cognizable ethical violation than sealing unreviewed plans prepared by registered subordinates, because in the former case the public is exposed not merely to unverified work but to work that has never been subjected to any independent professional quality gate, compounding the harm beyond what the Board's binary finding captures.

The board concluded that Engineer A bore affirmative restructuring obligations - specifically to require subordinate registered engineers to seal their own segments, reduce project volume, or decline to seal unreviewed work - and that his passive continuation of an inadequate supervisory model constitutes not merely a failure to review but a failure of professional integrity, because a conscientious engineer would have recognized organizational scale as a structural problem demanding structural solutions rather than treating it as an excuse that dissolves the responsible charge obligation.

The board concluded that while Engineer A's failure to review registered subordinates' work is a serious ethical violation, the violation is categorically more severe with non-registered subordinates because no licensed professional judgment exists at any stage prior to the seal, making the seal itself a misrepresentation of professional oversight that was never actually provided; the board's single unified finding, though correct, was held to understate this aggravated dimension.

The board concluded that Engineer A bears affirmative obligations to require subordinate registered engineers to seal their own segments under the Section II.2.c coordinating model, to refuse to seal non-registered engineers' work absent direct supervision, and - if the firm's scale renders these steps impossible - to decline the chief engineer sealing role or redistribute it, because inaction in the face of a known structural impossibility is itself an independent ethical failure.

The board concluded that sealing non-registered graduate engineers' plans under only general supervision is not merely a procedural shortcut but a substantive misrepresentation - the seal falsely certifies professional oversight that was never provided - and that this distinction warrants a separate and more stringent ethical finding beyond the board's unified conclusion, because the Dual-Mode Seal Authorization Principle imposes a heightened standard precisely to compensate for the absence of the subordinate's own licensure accountability.

The board concluded that the Chief Engineer Managerial Responsible Charge Standard and the Detailed Review Sufficiency Standard are not in genuine conflict but operate at different stages of the same unified obligation: Engineer A's conceptual and consultative contributions are necessary preconditions for meaningful review but cannot substitute for it, and the boundary between legitimate managerial oversight and insufficient review is drawn at the point where the sealing engineer can form an independent professional judgment that the completed work conforms to design intent, applicable standards, and public safety requirements.

The board concluded that the tension between the Subordinate Competence Confidence Non-Substitution Principle and the Technical Segment Sealing by Qualified Preparers principle is real but resolvable through the Section II.2.c multi-seal model: when subordinate registered engineers formally certify their own segments, Engineer A's coordinating seal no longer rests on unverified trust but on documented professional accountability, making his coordination role ethically sound - and the conflict persists only so long as Engineer A maintains a sole-sealing structure that makes his own verification structurally impossible.

The Board concluded that Engineer A's ethical failure was both anterior and ongoing: he should have accepted the chief engineer role only on the condition that the firm would be restructured to make responsible charge achievable, and having failed to impose that condition, he then compounded the threshold violation by continuing to seal plans without adequate review - though the Board's formal findings addressed only the downstream dimension, leaving the anterior violation analytically identified but formally unresolved.

The Board concluded that the apparent conflict between the coordinating engineer provision and the Professional Judgment Certification principle dissolves under careful mutually dependent reading: Section II.2.c is not a license for a single engineer to seal an entire large project without detailed review or subordinate seals, but rather a framework that presupposes a multi-seal model in which the coordinating seal certifies integration while subordinate seals certify segment-level competence - a model Engineer A failed to implement.

The Board concluded from a deontological perspective that Engineer A's breach was categorical and unambiguous: by substituting a relational attitude (confidence in subordinates) for a cognitive act (personal verification and judgment), he committed a categorical error that the Kantian universalizability test confirms - a world in which all chief engineers followed his maxim would render the entire sealing institution incoherent, demonstrating that the maxim cannot be morally permissible.

The Board concluded from a consequentialist perspective that the systemic and distributional harms of Engineer A's practice decisively outweigh the organizational efficiency gains: beyond the immediate risk calculus, the normalization of sealing without review would degrade the entire information architecture of professional licensure, harming the public's ability to rely on the seal as a proxy for actual professional oversight - a harm that the efficiency gains, which are real but bounded, cannot justify.

The Board concluded from a virtue ethics perspective that Engineer A's failure was not merely a discrete act but a failure of practical wisdom and professional integrity: by habituating the rationalization that organizational scale excuses him from detailed review, he expressed and reinforced a character disposition that a truly conscientious engineer would resist - and the virtue ethics framework adds the dimension that this habituation makes future compliance progressively less likely, compounding the ethical failure over time in a way that neither deontological nor consequentialist analysis fully captures.

The board concluded that Sections II.2.a, II.2.b, and II.2.c, read together, impose a unified pre-acceptance obligation on Engineer A to assess whether the role's conditions permit responsible charge, and that accepting the role without that capacity constitutes a threshold ethical violation independent of whether any actual harm resulted - because the non-delegable nature of professional accountability means the violation is complete at the moment of role acceptance under impossible conditions.

The board concluded that a restructured multi-seal model would substantially satisfy the responsible charge standard because Section II.2.c's coordinating provision sets a role-appropriate - not reduced - standard, and Engineer A's actual activities would constitute genuine coordination-level responsible charge if subordinate registered engineers formally sealed their own segments; the board further identified Engineer A's failure to implement or advocate for this model as a significant and independent dimension of his ethical failure.

The board concluded that the firm's operational model was not ethically viable for non-registered subordinate work at its current scale because the NCEE Model Law's direct control and personal supervision requirement is mandatory and non-negotiable, and the firm's failure to employ sufficient registered engineers in supervisory roles - rather than Engineer A's individual capacity - was the structural root of the ethical violation.

The board concluded that applying Case 85-3 reasoning, Engineer A's acceptance of the chief engineer role under structurally impossible conditions was the single anterior decision generating all subsequent violations, and that refusing the role would have compelled the firm to adopt a multi-engineer sealing model or reduce scale - outcomes more protective of the public than the status quo of ongoing unreviewed sealing.

The board concluded that a genuinely substantive mandatory checkpoint review system would satisfy the responsible charge standard for large organizations, confirming the standard is workable but demanding, and that the firm's failure to implement such a system - rather than any inherent impossibility - was the source of the ethical violation, because the costs of professional accountability must be borne by the organization, not transferred to the public through unverified sealing.

The Board concluded that Engineer A's sealing was unethical because, while managerial contributions are professionally meaningful and constitute the floor of engagement, they do not satisfy the document-level verification obligation that the act of sealing imposes; the seal is a document-level certification requiring document-level review, and Engineer A's failure to distinguish between his role-level contributions and his document-level obligations was the operative ethical error.

The Board concluded that the apparent conflict between the Non-Substitution Principle and the Technical Segment Sealing principle was not a genuine logical contradiction but a symptom of a flawed practice architecture, and that the ethical resolution required Engineer A to restructure the firm's sealing practice so that registered subordinate engineers seal the segments they prepare while Engineer A seals only what he has personally reviewed or assumes a genuinely restructured coordination role under Section II.2.c.

The Board concluded that Engineer A's ethical failure was not merely a series of improper sealings but a foundational violation committed at the moment of role acceptance, when he undertook a chief engineer position whose organizational scale made responsible charge over all sealed documents structurally impossible to discharge; the downstream sealing violations are symptomatic of that threshold failure, and the resolution implies that the firm's operational model - not merely Engineer A's individual conduct - required structural reformation to make ethical compliance achievable.

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?

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?

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?

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?

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?

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?

Should Engineer A continue sealing plans based on his managerial oversight and confidence in subordinates' competence, implement a mandatory checkpoint review system requiring detailed personal review of each project before sealing, or decline to seal any document he has not personally reviewed in sufficient detail?

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?

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?

Should Engineer A continue sealing plans under a general managerial oversight model, restructure the firm's sealing practice to require subordinate registered engineers to affix their own seals to segments they prepare, or decline to seal any plans he has not personally reviewed in detail?