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 as the primary precedent addressing the sealing of plans prepared by others under an engineer's direction, and then clarified/modified its earlier conclusion to better reflect actual engineering practice.

It was ethical for Engineer A, a registered professional engineer to sign and seal documents he prepared using a CADD system.

It was ethical for Engineer B, a registered professional engineer, to sign and seal documents which are the work of others using a CADD system working under his direction and control.

Beyond the Board's finding that Engineer A may ethically seal CADD-prepared documents, the ethical validity of that seal is implicitly conditioned on Engineer A possessing sufficient competence in the specific CADD system used to detect systematic errors, misapplied parameters, or software-induced distortions in the output. Technology-neutrality does not dissolve the competence prerequisite embedded in the Code; it merely relocates it. Where hand-drafting required mastery of manual technique, CADD use requires mastery of the tool's logic, limitations, and failure modes. An engineer who seals CADD output without the ability to critically evaluate whether that output faithfully represents sound engineering judgment has not merely used a new medium - they have delegated a portion of their professional judgment to the software itself, which the Technology-as-Tool Non-Substitution principle prohibits. Accordingly, the Board's approval of Engineer A's sealing practice should be understood as approval contingent on demonstrated CADD competence, not as a blanket endorsement of sealing regardless of the engineer's familiarity with the system employed.

The Board's approval of Engineer A's sealing practice carries an implicit and ongoing obligation: as CADD technology evolves - incorporating new automation layers, parametric modeling, or AI-assisted generation - Engineer A's ethical authorization to seal documents produced by those systems does not automatically persist. Each material advancement in the tool's capability that outpaces the engineer's trained understanding creates a new competence gap that must be closed before sealing is ethically permissible. The Board's reasoning, grounded in the premise that CADD is a drafting tool under the engineer's control, becomes strained when the tool begins making autonomous design decisions the engineer cannot independently verify. The ethical standard therefore demands periodic re-validation of competence as a living obligation, not a one-time qualification. Failure to maintain that currency while continuing to seal documents produced by unfamiliar system versions or capabilities would constitute a violation of the professional competence standard even if the engineer's original CADD training was adequate at the time of adoption.

The Board's modification of the stricter BER Case 86-2 standard - which had required detailed personal review before sealing - reflects a principled recognition that imposing an impossible standard on team-based CADD workflows would be both practically destructive and ethically counterproductive. However, this modification introduces a critical analytical nuance the Board did not fully articulate: the relaxation of the detailed-review requirement for Engineer B does not reduce the substantive depth of responsible charge; it redefines the mechanism through which that charge is exercised. Engineer B's ethical obligation migrates from post-hoc document review to upstream direction and control - meaning that the ethical weight of the seal is borne by the quality of Engineer B's supervisory engagement throughout the production process, not merely by a final inspection of the completed document. This reframing means that Engineer B who provides robust directional guidance, establishes clear technical parameters, and maintains meaningful engagement with subordinates' work throughout its development satisfies responsible charge even without line-by-line review, while Engineer B who provides only nominal supervision and relies on a cursory final glance does not - regardless of whether the finished document appears correct. The distinction between genuine responsible charge and its mere appearance is therefore the central ethical fault line the Board's ruling implicitly draws.

The Board's dual-mode authorization - treating Engineer A's self-authored sealing and Engineer B's supervisory sealing as ethically equivalent outcomes - obscures a fundamental asymmetry in the epistemic basis for each engineer's confidence in the sealed document. Engineer A, having personally prepared the work, possesses direct first-person knowledge of every design decision embedded in the CADD output. Engineer B, by contrast, possesses only mediated knowledge derived through the supervisory relationship. This epistemic asymmetry does not render Engineer B's sealing ethically impermissible - the Code explicitly accommodates it through the direction-and-control provision - but it does mean that Engineer B bears a qualitatively different and arguably heavier burden of professional accountability. Because Engineer B's knowledge of the document's technical content is necessarily less granular than Engineer A's, Engineer B must compensate through the rigor of the supervisory process itself: establishing clear technical standards, verifying subordinates' qualifications, reviewing critical decision points, and maintaining sufficient engagement to detect errors that subordinates may not recognize as such. The ethical equivalence of the two sealing modes is therefore a functional equivalence in outcome and authorization, not a substantive equivalence in the nature or depth of the professional obligation each engineer must discharge.

The Board's reasoning, while addressed to CADD technology specifically, implicitly establishes an ethical framework that will govern the profession's encounter with increasingly autonomous design tools, including AI-assisted systems that generate not merely drafting output but substantive engineering calculations and design decisions. The critical ethical variable the Board identifies is not the technology's nature but the engineer's meaningful exercise of professional judgment over the output. As that judgment becomes harder to exercise - because the tool's reasoning is opaque, its outputs voluminous, or its autonomous decisions difficult to independently verify - the ethical permissibility of sealing becomes correspondingly more contingent on the engineer's ability to interrogate and validate the system's work. The Board's technology-neutral framework therefore contains within it a technology-sensitive limit: at the point where an engineer can no longer exercise genuine direction and control over a system's outputs, the ethical authorization to seal those outputs dissolves, regardless of whether the system is labeled a drafting tool, a design assistant, or an autonomous engineering agent. The profession should treat this implicit limit as a forward-looking constraint that conditions the adoption of any new technology on the preservation of the engineer's capacity for independent professional judgment.

In response to Q101, the Board's framework implies that the competence threshold for sealing CADD-generated documents is not a fixed, externally certified standard but rather a functional one: an engineer must possess sufficient understanding of the CADD system's outputs to independently evaluate their technical accuracy, identify errors, and exercise professional judgment about the work's completeness and correctness. This threshold is not met merely by being able to operate the software; it requires the capacity to critically assess what the software produces. The burden of verifying that this threshold has been met rests primarily on the sealing engineer themselves, consistent with the self-regulatory character of professional licensure. However, when Engineer B supervises subordinates using CADD, a secondary verification obligation arises at the organizational level: Engineer B must have sufficient CADD competence to evaluate the work produced by those subordinates, not merely to manage the workflow. Neither the Board nor the Code delegates this verification to a third party, meaning the sealing engineer bears sole ethical responsibility for confirming their own qualifying competence before affixing a seal.

In response to Q102, when CADD software contains an undetected algorithmic error that propagates through subordinates' work and Engineer B seals those documents without discovering the error, ethical culpability should be apportioned according to the degree of control and the foreseeability of the failure mode. Engineer B bears primary professional and ethical responsibility because the seal represents a personal attestation of technical adequacy; the responsible charge obligation is not discharged merely because an error originated in software rather than in human drafting. The subordinates bear a secondary ethical obligation to flag anomalous outputs and to exercise independent technical judgment rather than uncritically accepting CADD-generated results. The software vendor bears legal product liability but not professional ethical culpability under the engineering code, because the vendor is not a licensed professional exercising responsible charge. Critically, the existence of a software error does not transfer Engineer B's ethical obligation to the vendor; the engineer's duty to review and verify outputs is precisely the safeguard intended to catch such errors. If the error was genuinely undetectable through reasonable professional review, Engineer B's culpability is mitigated but not eliminated, because the competence prerequisite includes understanding the known limitations and failure modes of the tools employed.

In response to Q103, the Board's approval of CADD-assisted sealing does implicitly establish a continuing competence obligation that evolves with the technology. Because the ethical validity of the seal rests on the engineer's capacity to evaluate the CADD system's outputs, and because CADD systems change in capability, interface, and error profile across versions, an engineer who seals documents produced by a system version or capability they have not been trained on cannot satisfy the competence prerequisite. The ethical consequence is that sealing under such conditions would constitute a violation of the obligation to undertake assignments only when qualified by education or experience, even if the engineer holds a valid license and was previously competent on an earlier version of the same software. This does not require formal re-certification, but it does require that engineers proactively assess whether their existing competence extends to new tools or upgraded systems before using them as the basis for sealed documents. Failure to do so transforms the seal from a professional attestation into a procedural formality, undermining the moral authority the seal is intended to convey.

In response to Q104, the responsible charge standard does not categorically require Engineer B to review each individual contributor's discrete portion of the work in isolation, but it does require that the integrated final document be reviewed with sufficient depth to detect errors that any individual contributor may have introduced. A purely holistic review of the final document is ethically sufficient only if Engineer B possesses the technical competence to identify errors that would be visible at the integrated level. However, where the work is modular and errors in one contributor's portion would not be apparent in the final integrated output without examining that portion specifically, a holistic review alone would be inadequate to satisfy the direction-and-control standard. The ethical obligation therefore scales with the architecture of the work: tightly integrated documents may permit holistic review, while modular or independently developed components require targeted review of each contributor's work. This interpretation is consistent with the Board's modification of BER Case 86-2, which rejected an impossibly strict standard while preserving the substantive requirement that the sealing engineer genuinely understand and be accountable for the technical content of the sealed documents.

In response to Q201, the tension between technology-neutral seal validity and the detailed review sufficiency standard is real and not merely theoretical. When CADD output volume or complexity makes genuinely detailed review practically impossible within normal professional workflows, technology-neutrality risks becoming a shield for inadequate oversight rather than a principled equivalence between drafting methods. The resolution lies in recognizing that technology-neutrality does not mean that the review obligations attached to sealing are themselves technology-neutral: the engineer must adapt their review methodology to the characteristics of CADD output, including its scale, its error modes, and its integration complexity. If the volume of CADD-generated documents is so large that no meaningful review is possible, the ethical answer is not to invoke technology-neutrality to justify sealing all of them, but rather to limit the scope of sealed work to what can be genuinely reviewed. The Board's rejection of an impossible standard in BER Case 86-2 cuts in both directions: it relieves engineers of unrealistic review burdens, but it does not license sealing documents that have not been reviewed at all.

In response to Q202, the Precedent Reconciliation Obligation derived from BER Case 86-2 and the Ethics Code Prevailing Practice Consonance principle are not in irreconcilable conflict, but they do require a principled methodology for updating ethical standards as technology evolves. The Board's modification of BER Case 86-2 in the current case demonstrates that precedent is not immutable when the factual assumptions underlying it have been overtaken by technological change. However, deference to precedent serves important values of predictability and consistency, and the threshold for departing from it should be high: the factual change must be material to the ethical reasoning, not merely incidental. As CADD and AI capabilities continue to evolve, the profession faces a recurring obligation to reassess whether existing ethical standards remain consonant with actual practice. The danger of uncritical deference to precedent is that it entrenches standards calibrated to obsolete technology, while the danger of too-ready departure from precedent is that it allows prevailing practice to define ethics rather than the reverse. The appropriate balance is to treat precedent as presumptively valid but rebuttable when technological change materially alters the conditions under which the original ethical judgment was made.

In response to Q203, the apparent paradox between the Technology-as-Tool Non-Substitution principle and the Competence Assurance Under CADD Tool Adoption principle dissolves when the two principles are properly scoped. Deep CADD proficiency is not in tension with independent professional judgment; rather, it is a precondition for exercising that judgment effectively in a CADD-enabled practice environment. The Non-Substitution principle prohibits the engineer from treating CADD outputs as self-validating or from allowing the software's authority to displace their own technical reasoning. The Competence Assurance principle requires that the engineer understand the tool well enough to use it reliably. These principles operate at different levels: competence is about knowing how the tool works and what it produces, while non-substitution is about ensuring that the engineer's independent judgment remains the final arbiter of technical adequacy. An engineer who is highly proficient in CADD but who critically evaluates its outputs against their own engineering knowledge satisfies both principles simultaneously. The paradox only arises if competence is misunderstood as deference to the tool, which it is not.

In response to Q204, the tension between the Responsible Charge Integrity principle and the Dual-Mode Seal Authorization principle is genuine and reflects a real asymmetry in the epistemic basis for the two modes of sealing. When Engineer A seals documents they personally prepared, the seal rests on direct first-hand knowledge of every technical decision embedded in the document. When Engineer B seals documents prepared by subordinates, the seal rests on a combination of directional oversight, review of outputs, and trust in the competence of those supervised. These are not epistemically equivalent, and treating them as ethically equivalent under the Dual-Mode framework requires that Engineer B's direction-and-control be substantive enough to compensate for the absence of personal preparation. The ethical equivalence is therefore conditional, not absolute: it holds only when Engineer B's supervisory engagement is sufficiently active and technically informed to produce a level of confidence in the document's accuracy that approximates what personal preparation would provide. Where that condition is not met, the Dual-Mode equivalence collapses and Engineer B's seal becomes ethically deficient regardless of the formal authorization the framework provides.

In response to Q301, from a deontological perspective, Engineer B's duty to exercise responsible charge requires more than general directional oversight but does not require personal line-by-line review of every element of CADD-generated documents. The categorical obligation is to be able to truthfully attest, through the act of sealing, that the documents reflect competent engineering work for which the sealing engineer accepts full professional responsibility. This attestation is only honest if Engineer B has engaged with the technical content sufficiently to form an independent judgment about its adequacy. The deontological framework therefore sets a threshold of substantive technical engagement, not a procedural checklist: the duty is satisfied when Engineer B's review is genuine enough to support the moral claim embedded in the seal, and violated when the seal is affixed as a formality without that genuine engagement. The direction-and-control standard articulated in Code Section II.2.c is best understood deontologically as a structural condition that makes honest sealing possible, not as a substitute for the underlying duty of honest attestation.

In response to Q302, from a consequentialist perspective, the Board's permissive standard for Engineer B's supervisory sealing is likely to produce better aggregate outcomes for public safety than a strict personal-preparation requirement, provided that the direction-and-control condition is genuinely enforced. A strict personal-preparation rule would create severe bottlenecks in engineering production, concentrate sealing authority in ways that reduce the diversity of technical review, and potentially discourage adoption of CADD technology that, when properly used, reduces drafting errors and improves document quality. The supervisory model, by contrast, allows engineering teams to leverage specialized competencies while maintaining a single accountable professional who integrates and validates the work. However, the consequentialist case for the permissive standard depends critically on the quality of supervisory oversight actually exercised: if the direction-and-control requirement becomes a nominal formality, the public safety benefits of the supervisory model evaporate and the permissive standard produces worse outcomes than the strict alternative. The consequentialist analysis therefore supports the Board's standard conditionally, and implies that robust enforcement of the substantive direction-and-control requirement is essential to the standard's ethical justification.

In response to Q303, from a virtue ethics perspective, Engineer A demonstrates professional integrity when sealing CADD-generated documents only if the use of CADD is integrated into a practice of active technical engagement rather than passive acceptance of software outputs. The virtue at stake is intellectual honesty: the engineer must genuinely believe, on the basis of their own technical judgment, that the documents are accurate and complete before affixing a seal that represents that belief to the world. CADD tools that automate drafting do not threaten this virtue as long as the engineer retains the capacity and the habit of critically evaluating what the tools produce. The erosion of independent engineering judgment that virtue ethics warns against occurs not through the use of CADD per se, but through the gradual atrophy of the engineer's own technical reasoning when it is never exercised because the software always provides an answer. The virtuous CADD-using engineer therefore maintains their independent technical competence not as a redundant check on the software but as the primary basis for professional judgment, with CADD serving as a tool that extends that judgment rather than replacing it.

In response to Q304, from a virtue ethics perspective, Engineer B exhibits genuine professional courage and accountability when sealing CADD documents prepared by subordinates only if the act of sealing reflects authentic ownership of the work rather than a procedural delegation of risk. The virtue of accountability requires that Engineer B be willing to stand behind the technical content of the sealed documents as if they had prepared them personally, which in turn requires that Engineer B's supervisory engagement be deep enough to make that stance intellectually honest. The risk of moral diffusion across the engineering team is real: when multiple subordinates contribute to a document and Engineer B reviews the integrated output, it is psychologically easy for each participant to assume that someone else has caught any errors, producing a collective failure of accountability that no individual feels responsible for. The virtuous response to this risk is for Engineer B to cultivate a supervisory practice that explicitly assigns and verifies individual accountability within the team, while personally assuming ultimate responsibility through the seal. Where Engineer B seals documents as a procedural formality without this genuine ownership, the seal becomes a moral fiction that undermines the profession's claim to public trust.

In response to Q401, had the Board not modified the stricter standard of BER Case 86-2 requiring detailed personal review before sealing, Engineer B's conduct of sealing CADD documents prepared by subordinates under general direction and control would have been deemed unethical under that earlier standard. The practical consequences for engineering firms relying on team-based CADD production workflows would have been severe: either firms would have been required to have the sealing engineer personally review every technical detail of every document, creating unsustainable bottlenecks and effectively prohibiting the division of labor that makes large-scale engineering projects feasible, or firms would have continued their existing practices while technically violating the ethical standard, producing a widespread gap between formal ethics and actual professional conduct. The Board's modification was therefore not merely a clarification but a substantive recalibration of the responsible charge standard to reflect the realities of modern engineering practice. This recalibration was ethically justified because the stricter standard, applied literally to CADD-enabled team workflows, would have imposed an impossible burden that served no additional public safety purpose beyond what genuine direction-and-control supervision already provides.

In response to Q402, if Engineer A had used an AI-assisted design system that autonomously generated structural calculations and layout decisions rather than a CADD system that merely automated drafting, the Board's technology-neutral reasoning would not straightforwardly support the ethical validity of Engineer A's seal without significant qualification. The critical distinction is between tools that automate the execution of engineering decisions already made by the engineer and tools that autonomously generate the engineering decisions themselves. CADD in its traditional form falls in the former category: it automates drafting but does not substitute for the engineer's structural analysis, design judgment, or technical decision-making. An AI system that autonomously generates structural calculations introduces a qualitatively different challenge: the engineer sealing the documents must be able to independently verify the correctness of machine-generated engineering judgments, not merely review the accuracy of machine-executed drafting. If the AI's reasoning is opaque or its outputs cannot be independently verified through the engineer's own technical analysis, the seal would lack the epistemic foundation that makes it ethically valid. The Board's technology-neutral framework therefore has implicit limits: it applies to tools that extend the engineer's capacity to execute decisions, but requires additional scrutiny when applied to tools that purport to make engineering decisions autonomously.

In response to Q403, if Engineer B had failed to exercise meaningful direction and control - approving CADD documents prepared by subordinates without reviewing their technical content - the seal affixed by Engineer B would constitute an ethical violation equivalent in character to the misconduct identified in BER Case 86-2, and potentially more serious given the explicit direction-and-control requirement in Code Section II.2.c. The profession must distinguish genuine responsible charge from its appearance by reference to the substantive quality of the engineer's engagement with the technical content: genuine responsible charge requires that the sealing engineer be able to articulate the technical basis for the work, identify the key design decisions embedded in the documents, and explain why those decisions are appropriate. An engineer who cannot do these things has not exercised responsible charge regardless of the organizational structure nominally in place. The appearance of supervisory oversight - attending project meetings, signing off on deliverables, being listed as the engineer of record - does not satisfy the ethical standard if it is not accompanied by genuine technical engagement. Distinguishing genuine from nominal responsible charge requires examining the engineer's actual knowledge of the work's technical content, not merely their formal role in the project hierarchy.

In response to Q404, if Engineer A lacked sufficient competence in the specific CADD system used to produce the documents - being unable to detect systematic errors introduced by the software - the seal would not be ethically valid under the Board's framework, even though that framework is formally technology-neutral. The technology-neutral principle establishes that CADD-generated documents are not inherently inferior to hand-drafted ones and that the medium of production does not itself disqualify a document from being sealed. But technology-neutrality does not suspend the competence prerequisite; it operates within it. The ethical validity of the seal depends on the engineer's capacity to evaluate the technical content of the documents, and that capacity is tool-specific when the tool is capable of introducing systematic errors that are not apparent without understanding the tool's behavior. This effectively creates a technology-specific qualification requirement that conditions the permissibility of sealing: an engineer who is technically competent in the underlying engineering discipline but incompetent in the specific CADD system used cannot ethically seal documents produced by that system, because they lack the means to verify that the system has not introduced errors. This conclusion is consistent with Code Section II.2.a, which requires qualification by education or experience in the specific technical field, interpreted to include the tools through which that technical work is executed.

The Board resolved the tension between Technology-Neutral Seal Validity and the Detailed Review Sufficiency Standard not by eliminating the review requirement but by recalibrating what 'sufficient' review means in light of how CADD work is actually produced. Rather than demanding that a sealing engineer personally retrace every drafting step, the Board accepted that competent direction and control over the process - setting parameters, verifying outputs, and exercising independent technical judgment at key decision points - satisfies the review obligation. This resolution teaches that the Detailed Review Sufficiency Standard is not a fixed procedural checklist but a purposive standard: its purpose is to ensure the engineer genuinely understands and vouches for the document's technical content, and that purpose can be fulfilled through supervisory engagement as well as personal drafting. The risk flagged in Q201 - that technology-neutrality becomes a shield for inadequate oversight - is real but is addressed by insisting that direction and control be substantive, not nominal. Technology-neutrality therefore operates as a permissive principle that expands the range of acceptable workflows, while Detailed Review Sufficiency operates as a limiting principle that prevents that permission from collapsing into rubber-stamping.

The Board's modification of BER Case 86-2 illustrates how the Precedent Reconciliation Obligation and the Ethics Code Prevailing Practice Consonance principle interact when factual circumstances evolve. The earlier case's stricter standard - prohibiting sealing without detailed personal review - was not wrong on its own terms; it reflected the epistemic conditions of a drafting environment where supervision was harder to verify and CADD workflows were novel. By the time of the instant case, CADD had become sufficiently integrated into professional practice that treating it as categorically different from hand-drafting would have imposed an impossible standard on legitimate engineering workflows. The Board's reasoning implicitly establishes a meta-principle: ethical standards derived from precedent must be tested against the factual assumptions that gave them their justificatory force, and when those assumptions no longer hold, fidelity to the underlying ethical value - ensuring engineers genuinely own what they seal - requires updating the standard rather than mechanically applying the old rule. This has direct implications for Q202 and Q402: as AI-assisted design systems increasingly generate not just drafting output but substantive engineering judgments, the same meta-principle demands that the direction-and-control standard be re-examined again, because the epistemic gap between the sealing engineer and the document's technical content may widen to a point where the current standard no longer reliably secures the underlying value.

The most structurally significant tension in this case is between the Dual-Mode Seal Authorization principle - which treats Engineer A's self-authored sealing and Engineer B's supervisory sealing as ethically equivalent - and the Responsible Charge Integrity principle, which demands that the seal represent genuine personal accountability for the document's technical soundness. These two principles are reconcilable only if the Competence Assurance Under CADD Tool Adoption principle and the Technology-as-Tool Non-Substitution principle are treated as jointly necessary conditions that both engineers must satisfy. The reconciliation works as follows: Engineer A's seal is ethically valid because personal preparation, combined with CADD competence and preserved independent judgment, gives Engineer A direct epistemic access to the document's content. Engineer B's seal is ethically valid because substantive direction and control, combined with CADD competence and active technical engagement, gives Engineer B a functionally equivalent - though structurally different - epistemic basis for accountability. The paradox identified in Q203, where deep CADD reliance simultaneously satisfies competence requirements and risks substituting machine output for professional judgment, is resolved by insisting that competence in CADD means knowing when and how to override, verify, and critically interrogate the system's output, not merely knowing how to operate it. The Technology-as-Tool Non-Substitution principle thus functions as an internal constraint on what counts as genuine CADD competence, preventing the Competence Assurance principle from being satisfied by mere operational fluency. Together, these four principles establish that the ethical validity of sealing in either mode depends on the engineer maintaining an independent technical judgment that the CADD system serves but does not replace.

Was it ethical for Engineer A, a registered professional engineer to sign and seal documents he prepared using a CADD system?

Was it ethical for Engineer B, a registered professional engineer, to sign and seal documents which are the work of others using a CADD system, working under his direction and control?

At what minimum level of CADD competence must Engineer A and Engineer B demonstrate proficiency before they are ethically permitted to sign and seal CADD-generated documents, and who bears responsibility for verifying that competence threshold has been met?

If CADD software contains an undetected algorithmic error that propagates through Engineer B's subordinates' work, and Engineer B seals those documents without discovering the error, how should professional liability and ethical culpability be apportioned between Engineer B, the subordinates, and the software vendor?

Does the Board's approval of CADD-assisted sealing implicitly establish an obligation for engineers to periodically re-validate their CADD competence as the technology evolves, and what ethical consequences follow if an engineer seals documents using a CADD system version or capability they have not been trained on?

When CADD output is produced collaboratively by multiple subordinates under Engineer B's direction, does the ethical obligation of responsible charge require Engineer B to review each individual contributor's portion of the work, or is a holistic review of the integrated final document sufficient to satisfy the direction-and-control standard?

Does the Technology-Neutral Seal Validity principle, which permits sealing of CADD-generated documents on equal footing with hand-drafted ones, conflict with the Detailed Review Sufficiency Standard when CADD output volume or complexity makes genuinely detailed review practically impossible, thereby risking that technology-neutrality becomes a shield for inadequate oversight?

How should the Precedent Reconciliation Obligation derived from BER Case 86-2 be balanced against the Ethics Code Prevailing Practice Consonance principle when evolving CADD and AI capabilities render the earlier case's factual assumptions obsolete, and does deference to precedent risk entrenching an ethical standard that no longer reflects the realities of modern engineering practice?

Does the Technology-as-Tool Non-Substitution principle, which demands that engineers preserve independent professional judgment and not treat CADD as a crutch, conflict with the Competence Assurance Under CADD Tool Adoption principle when deep reliance on CADD functionality is itself the mark of competent modern practice, creating a paradox where greater CADD proficiency may simultaneously satisfy one principle while threatening the other?

When the Responsible Charge Integrity principle invoked by Engineer B's supervisory mode demands active engagement and detailed review, does it come into irreconcilable tension with the Dual-Mode Seal Authorization principle that treats Engineer A's self-authored sealing and Engineer B's supervisory sealing as ethically equivalent, given that the epistemic basis for confidence in document accuracy differs fundamentally between the two modes?

From a deontological perspective, does Engineer B's duty to exercise responsible charge require a specific threshold of detailed technical review before sealing CADD-generated documents prepared by subordinates, or is general supervisory direction and control sufficient to satisfy that categorical obligation?

From a consequentialist perspective, does permitting Engineer B to seal CADD documents prepared by subordinates under direction and control produce better outcomes for public safety than a stricter rule requiring personal preparation, given that such a rule might discourage adoption of productivity-enhancing technology or concentrate sealing authority in ways that reduce overall engineering output quality?

From a virtue ethics perspective, does Engineer A demonstrate the professional integrity and intellectual honesty expected of a competent engineer when sealing CADD-generated documents, particularly with respect to ensuring that reliance on automated drafting tools does not erode the independent engineering judgment that gives the seal its moral authority?

From a virtue ethics perspective, does Engineer B exhibit the character trait of professional courage and accountability when assuming full responsibility for CADD documents prepared by others under their direction, and does the act of sealing such documents reflect genuine ownership of the work or merely a procedural formality that could mask a diffusion of moral responsibility across the engineering team?

If the Board had not modified the stricter standard established in BER Case 86-2 - which prohibited sealing without detailed personal review - would Engineer B's conduct of sealing CADD documents prepared by subordinates under general direction and control have been deemed unethical, and what practical consequences would that stricter standard have imposed on engineering firms that rely on team-based CADD production workflows?

What if Engineer A had used an AI-assisted design system that autonomously generated structural calculations and layout decisions rather than a CADD system that merely automated drafting - would the Board's technology-neutral reasoning still support the ethical validity of Engineer A's seal, or would the degree of autonomous machine judgment require a different ethical standard for responsible charge?

If Engineer B had failed to exercise meaningful direction and control - for example, by approving CADD documents prepared by subordinates without reviewing their technical content - would the seal affixed by Engineer B constitute an ethical violation equivalent to the misconduct identified in BER Case 86-2, and how should the profession distinguish between genuine responsible charge and the mere appearance of supervisory oversight?

What if Engineer A lacked sufficient competence in the specific CADD system used to produce the documents - for instance, being unable to detect systematic errors introduced by the software - would the seal still be ethically valid under the Board's technology-neutral framework, or does the competence prerequisite effectively create a technology-specific qualification requirement that conditions the permissibility of sealing?

Engineer A signing and sealing their own CADD-generated work fulfills the self-authored document seal validity obligation and is guided by the technology-neutral seal validity principle, provided Engineer A maintains competence in CADD tools and does not allow the technology to substitute for professional judgment, with full professional responsibility assumed upon sealing.

Engineer B sealing documents prepared by others under their direction fulfills supervisory sealing obligations only when genuine responsible charge with detailed review is exercised, but violates those same obligations if sealing occurs without sufficient direction-and-control engagement, as distinguished from the prohibited general supervision scenario in BER Case 86-2.

Adopting a strict sealing interpretation that would require engineers to personally hand-draft every sealed document violates the ethics code's living-document obligation to align with prevailing CADD practice and is directly constrained by the BER's own prohibition against imposing impossible standards on practicing engineers.

Clarifying and modifying the 1986 ruling fulfills the BER's living-document obligation to align ethics guidance with prevailing CADD practice by affirming dual-mode seal authorization and detailed-review sufficiency, while remaining constrained by the enduring prohibition on general supervision without responsible charge and the requirement that technology never substitute for professional judgment.

This question emerged because the evolution from manual drafting to CADD created a gap in the sealing standard: existing ethics rules authorized sealing of self-prepared work without specifying tool-competence conditions, and Engineer A's action exposed that gap by making it unclear whether personal preparation via an automated system satisfies the same responsible-charge standard as manual preparation.

This question arose because Engineer B's supervisory sealing of CADD documents sits at the intersection of two contested standards-direction-and-control sufficiency and detailed-review necessity-and the introduction of CADD as an intermediary between Engineer B and the actual design work destabilized the prior consensus about what level of engagement satisfies responsible charge, forcing explicit ethical scrutiny.

This question emerged because the Board's permissive ruling on CADD sealing left a structural gap: it authorized the practice without specifying the competence floor that makes the authorization ethically coherent, and the two-engineer scenario made that gap visible by raising the question of whether Engineer A and Engineer B could be held to the same standard despite their different relationships to the CADD output.

This question emerged because CADD introduces a third-party algorithmic actor into the design chain whose errors can be invisible to both subordinates and supervising engineers, shattering the bilateral responsible-charge model (engineer and work product) that the sealing standard presupposes and forcing a new apportionment analysis that existing ethics frameworks were not designed to resolve.

This question emerged because the Board's ruling was temporally static-it approved CADD sealing at a moment in time-while CADD technology is dynamic, and the AI Anticipation Registered event made explicit that future tool capabilities will diverge substantially from those the ruling contemplated, creating a structural tension between the approval's implicit scope and the ongoing competence obligations that professional ethics impose on sealing engineers.

This question emerged because the evolution of CADD-enabled collaborative drafting created a factual situation not contemplated by earlier responsible charge standards written for individual or small-team authorship. The gap between the direction-and-control standard's text and the practical reality of multi-contributor CADD workflows forced a contest between two defensible interpretations of what 'detailed review' requires.

This question arose because the Technology-Neutral Seal Validity principle was formulated when CADD productivity gains were modest, but exponential increases in CADD and AI output volume have created conditions where the principle's application may systematically undermine the review standard it was never intended to displace. The conflict became visible only when technology outpaced the factual assumptions embedded in the neutrality principle.

This question emerged because BER Case 86-2 was decided in a technological environment where the chief engineer's supervision of hand-drafted or early CADD work was the paradigm case, and the subsequent proliferation of sophisticated CADD and AI tools has created a growing gap between that precedent's embedded assumptions and current practice. The question crystallized when practitioners recognized that faithful application of the precedent might entrench an ethical standard that no longer serves the public protection rationale that originally justified it.

This question emerged because the Technology-as-Tool Non-Substitution principle was articulated when CADD was a drafting aid supplementary to manual engineering judgment, but the maturation of CADD into an integrated design environment means that the tool now performs functions previously classified as professional judgment itself. The paradox became unavoidable when the competence standard evolved to require the very depth of CADD reliance that the non-substitution principle was designed to constrain.

This question arose because the Dual-Mode Seal Authorization principle was established to enable organizational efficiency in engineering practice, but it implicitly assumed that supervisory direction-and-control could produce epistemic confidence comparable to self-authorship. The question became pressing when CADD-enabled scale and complexity exposed the gap between the formal equivalence asserted by the Dual-Mode principle and the practical epistemic inequality between the two sealing modes, forcing a contest over whether the equivalence claim can survive scrutiny under the Responsible Charge Integrity standard.

This question emerged because the evolution of CADD-based team workflows created a structural gap between the categorical language of responsible charge doctrine and the practical reality of supervisory sealing, forcing a deontological reckoning over whether the duty is defined by the depth of personal technical engagement or by the quality of supervisory control exercised. The BER's modification of Case 86-2 resolved the institutional question but left the philosophical threshold - how much review is categorically required - contested and unanswered.

This question arose because the BER's moderation of the strict standard implicitly adopted a consequentialist justification - that overly restrictive rules harm engineering practice - without fully accounting for the countervailing consequentialist concern that relaxed standards may produce worse public safety outcomes at scale. The anticipation of AI-assisted design further amplified the stakes, making the outcome calculus more uncertain and the question more urgent.

This question emerged because CADD technology introduced an epistemic gap between the engineer's visible act of sealing and the invisible quality of their engagement with the tool's outputs, making it impossible to determine from the seal itself whether it reflects genuine independent judgment or passive ratification of automated drafting. The anticipation of AI-assisted design sharpened this concern, as increasingly autonomous tools make the boundary between engineer-as-author and engineer-as-approver progressively harder to locate.

This question arose because the supervisory sealing model creates a structural ambiguity between the outward performance of accountability - affixing a seal - and the inward virtue of genuine ownership, raising the concern that the seal may function as a moral shield that obscures rather than assigns responsibility within complex engineering teams. The BER's endorsement of direction-and-control sealing resolved the institutional question but left the virtue-ethics question of whether such sealing reflects character or merely compliance unresolved.

This question arose because the BER's modification of Case 86-2 created a retrospective ethical ambiguity: if the prior standard was wrong enough to require modification, then conduct that would have violated it was not straightforwardly unethical, yet if the modification was merely a pragmatic accommodation rather than a principled correction, then the prior standard retained moral authority that the modification cannot fully erase. The question forces a confrontation between the stability of ethical precedent and the adaptability of professional ethics to technological change.

This question arose because the Board's technology-neutral reasoning in the CADD context was premised on an implicit assumption that the tool executes but does not originate professional judgment, an assumption that AI-assisted autonomous design systems directly challenge by introducing a qualitatively different relationship between engineer and output. The Standard Interpretation Gap Identified event and AI Anticipation Registered event together expose that the existing warrant structure was calibrated for passive tools, leaving unresolved whether responsible charge can be meaningfully exercised - and a seal ethically affixed - when the machine itself performs the reasoning the engineer is supposed to supply.

This question arose because the BER Case 86-2 ruling condemned general supervision without detailed review but did not precisely define the threshold at which supervisory oversight becomes sufficiently substantive to constitute responsible charge, leaving a contested boundary between the Chief Engineer's condemned conduct and the direction-and-control model the Board endorsed for Engineer B. The Standard Interpretation Gap Identified event and the Sealing Standard Moderated event together reveal that the profession lacks a clear operational test for distinguishing genuine responsible charge from its simulacrum, making the question of what Engineer B must actually do before sealing an unresolved ethical problem.

This question arose because the Board's technology-neutral framework implicitly assumed that an engineer's general professional competence would transfer to any tool they chose to use, without recognizing that CADD systems can introduce systematic, tool-specific errors that are invisible to engineers unfamiliar with the software's behavior. The Drafting Technology Evolution event and the Standard Interpretation Gap Identified event together expose that technology-neutrality as a doctrinal position does not resolve the practical question of whether competence in the tool is a prerequisite for the responsible charge that makes sealing ethically valid, effectively forcing the technology-neutral principle to either absorb a technology-specific competence requirement or acknowledge that it cannot guarantee the professional accountability the seal is meant to certify.

The board concluded that Engineer A's sealing was ethical because CADD is merely a tool for executing engineering judgment that Engineer A himself exercised; since the Code's sealing obligation attaches to the engineer's competence and authorship rather than to the physical method of document production, substituting CADD for manual drafting does not disturb the ethical foundation of the seal.

The board concluded that Engineer B's sealing was ethical because Code provision II.2.c expressly authorizes engineers to assume responsibility for coordinated project work prepared by others, and because Engineer B's direction and control over subordinates' CADD work satisfied the responsible-charge standard even without the line-by-line personal review that BER Case 86-2 had previously required.

The board implicitly conditioned its approval of Engineer A's sealing on Engineer A possessing sufficient CADD competence to detect tool-specific errors, reasoning that the Code's competence requirement under II.2.a does not disappear when a new tool is adopted but instead demands mastery of that tool's logic and limitations as a precondition for ethically valid sealing.

The board extended its competence-conditioned approval into a forward-looking obligation, concluding that because the ethical validity of sealing rests on the engineer's ability to control and critically evaluate the tool's output, any material evolution in CADD capability that the engineer has not trained on creates a new ethical barrier to sealing that must be cleared through updated competence before the seal can again be ethically affixed.

The board concluded that Engineer B satisfies responsible charge not by reviewing every line of subordinates' CADD output but by exercising genuine upstream direction and control throughout the work's development, and that this reframing - from post-hoc review to proactive supervision - preserves the ethical integrity of the seal while accommodating the practical realities of team-based CADD production, provided the supervision is real rather than merely formal.

The board concluded that both sealing modes are ethically permissible but not substantively equivalent, because Engineer B's mediated knowledge of the work requires a more rigorous supervisory process - including standards-setting, qualification verification, and critical-point review - to achieve the same level of professional accountability that Engineer A's direct authorship provides automatically.

The board concluded that its technology-neutral framework implicitly encodes a technology-sensitive limit, such that the ethical permissibility of sealing AI- or CADD-generated outputs is always contingent on the engineer's demonstrable capacity to interrogate and validate those outputs, and that this limit should be treated as a forward-looking constraint governing the profession's adoption of any autonomous design tool.

The board concluded that the minimum competence threshold for sealing CADD-generated documents is functional and self-assessed - requiring the capacity to critically evaluate outputs and detect errors - and that this burden falls solely on the sealing engineer, with Engineer B bearing an additional obligation to possess sufficient CADD competence to evaluate subordinates' work rather than merely coordinate its production.

The board concluded that Engineer B bears primary ethical culpability for sealed documents containing undetected algorithmic errors because the duty to review and verify outputs is precisely the safeguard intended to catch such errors, that subordinates bear a secondary obligation of independent technical judgment, and that while genuine undetectability mitigates but does not eliminate Engineer B's culpability, the existence of a software error never transfers the engineer's professional obligation to the vendor.

The board concluded that the approval of CADD-assisted sealing implicitly establishes a continuing and technology-version-specific competence obligation, such that sealing documents produced by an unfamiliar or upgraded CADD system constitutes a violation of the qualification prerequisite regardless of licensure status, and that failure to proactively assess one's own competence before sealing degrades the seal from a professional attestation to a procedural formality.

The board concluded that responsible charge does not categorically demand discrete per-contributor review, but neither does it permit purely holistic review when the work is modular and errors would be invisible at the integrated level; the ethical obligation is therefore architecturally contingent, scaling the depth of required review to the structural characteristics of the CADD output so that Engineer B's direction-and-control remains substantive rather than nominal.

The board concluded that when CADD volume makes meaningful review impossible, the ethical answer is to limit the scope of sealed work rather than invoke technology-neutrality to justify sealing unreviewed documents, because technology-neutrality governs the permissibility of the drafting method but does not suspend the substantive review obligations that give the seal its professional meaning.

The board concluded that the Precedent Reconciliation Obligation and the Prevailing Practice Consonance principle are not irreconcilable but require a principled, high-threshold methodology for updating standards, demonstrated by the board's own modification of BER Case 86-2 in the current case, which treated precedent as presumptively valid while acknowledging that materially changed technological conditions can and should trigger reassessment.

The board concluded that the paradox between the Non-Substitution and Competence Assurance principles is illusory rather than genuine, because competence means understanding the tool well enough to critically evaluate its outputs, not deferring to them, and an engineer who achieves deep CADD proficiency while maintaining independent technical judgment satisfies both principles simultaneously without contradiction.

The board concluded that the tension between Responsible Charge Integrity and Dual-Mode Seal Authorization is genuine and reflects a real epistemic asymmetry between the two sealing modes, resolving it by treating the ethical equivalence of supervisory sealing as conditional - valid only when Engineer B's oversight is substantive enough to produce a level of confidence in document accuracy that approximates what personal preparation would provide, and collapsing into ethical deficiency when that condition is not met.

The board concluded that deontological duty does not demand personal line-by-line review but does demand that Engineer B's engagement be substantive enough to make the seal's implicit attestation of competent work truthful; the direction-and-control standard in II.2.c was interpreted as a structural precondition for honest sealing rather than a freestanding procedural substitute for the underlying duty of honest attestation.

The board concluded that permitting supervisory sealing produces better aggregate outcomes than a strict personal-preparation rule because it enables team-based specialization and CADD adoption, but explicitly conditioned this consequentialist endorsement on the direction-and-control requirement being genuinely enforced rather than treated as a nominal formality, without which the permissive standard would be ethically unjustifiable.

The board concluded that Engineer A demonstrates professional integrity when sealing CADD-generated documents provided that CADD is integrated into active technical engagement rather than passive acceptance of software outputs, because the virtue of intellectual honesty requires that the seal reflect a genuine independent belief in the document's accuracy grounded in the engineer's own technical reasoning rather than deference to the software.

The board concluded that Engineer B exhibits professional courage and accountability only when the act of sealing reflects authentic ownership of the technical content rather than procedural risk delegation, and that the virtue-ethics obligation requires Engineer B to cultivate supervisory practices that counteract moral diffusion by explicitly assigning and verifying individual accountability within the team while personally assuming ultimate responsibility through the seal.

The board concluded that under the unmodified BER Case 86-2 standard Engineer B's conduct would have been deemed unethical, but that the modification was substantively justified because the stricter standard, applied literally to CADD-enabled team workflows, would have either prohibited the division of labor essential to large-scale engineering or produced a widespread gap between formal ethics and actual practice, neither of which serves the public safety purpose the standard was designed to protect.

The Board resolved Q402 by drawing a categorical distinction between execution-automating tools and decision-generating tools, holding that the technology-neutral framework does not straightforwardly extend to AI systems that autonomously produce structural calculations because the sealing engineer must retain the independent capacity to verify those judgments - a capacity that opacity in AI reasoning may defeat, thereby undermining the epistemic foundation that makes the seal ethically valid.

The Board resolved Q403 by holding that an engineer who approves documents without reviewing their technical content has committed an ethical violation equivalent to - and potentially more serious than - the misconduct in BER Case 86-2, because the test for genuine responsible charge is whether the engineer can articulate the technical basis and key design decisions embedded in the work, not whether they occupied a supervisory role in the project hierarchy.

The Board resolved Q404 by holding that technology-neutrality does not override the competence prerequisite but operates within it, effectively creating a technology-specific qualification requirement: an engineer who is competent in the underlying engineering discipline but incompetent in the specific CADD system used cannot ethically seal those documents, because they lack the means to verify that the system has not introduced systematic errors - a conclusion grounded in Code Section II.2.a's requirement of qualification in the specific technical field, interpreted to encompass the tools of execution.

The Board resolved the tension in Q7 and the deontological question in Q11 by reframing the Detailed Review Sufficiency Standard as purposive rather than procedural - holding that its goal of ensuring genuine technical ownership can be met through competent direction and control over the process, including setting parameters, verifying outputs, and exercising independent judgment at key decision points, thereby permitting CADD-based team workflows while preventing technology-neutrality from collapsing into a license for rubber-stamping.

The Board resolved Q8 and the precedent tension by establishing a meta-principle: the modification of BER Case 86-2 was not a repudiation of its underlying ethical value - ensuring engineers genuinely own what they seal - but a recognition that fidelity to that value in changed factual circumstances required updating the standard from strict personal review to substantive direction and control, and the Board explicitly extended this meta-principle forward as a warning that AI-generated engineering judgments may again require the standard to be re-examined.

The board concluded that both Engineer A's and Engineer B's seals are ethically valid because each engineer maintains an independent technical judgment that the CADD system serves but does not replace - Engineer A through direct personal preparation and Engineer B through substantive supervisory direction and control - and that the apparent paradox between deep CADD reliance and preserved professional judgment is dissolved by defining genuine CADD competence as the capacity to critically interrogate and override system output, not merely to operate it fluently, so that the Technology-as-Tool Non-Substitution principle acts as an internal limiter preventing the Competence Assurance principle from being satisfied by operational skill alone.

Should Engineer A sign and seal engineering documents that Engineer A personally prepared using a CADD system, treating CADD as a production tool equivalent to hand-drafting, or should Engineer A refrain from sealing CADD-produced documents absent additional verification steps specific to the technology?

Should Engineer B sign and seal CADD-produced documents prepared by supervised subordinates under Engineer B's direction and control - relying on substantive supervisory engagement and detailed review as the basis for responsible charge - or must Engineer B personally prepare or conduct line-by-line technical review of every element before sealing?

Should Engineer A and Engineer B treat CADD competence as a self-assessed functional threshold - requiring the capacity to critically evaluate outputs and detect tool-specific errors - or should they condition sealing on externally verified proficiency standards, and must that competence obligation be periodically re-validated as CADD technology evolves?

When Engineer B seals CADD documents containing an undetected error propagated through subordinates' work, should Engineer B accept full primary professional and ethical responsibility for the error as an unqualified consequence of sealing, or should Engineer B's culpability be assessed proportionally based on the quality of supervisory engagement and the detectability of the error through reasonable professional review?

Should the Board treat its modification of BER Case 86-2 as establishing a stable technology-neutral framework for all future design-generation tools - including AI systems that autonomously produce engineering calculations - or should the Board articulate a technology-sensitive limit that conditions the ethical validity of sealing on the engineer's capacity to independently verify the tool's substantive engineering judgments?

Should Engineer B treat the Dual-Mode Seal Authorization principle as conferring ethical equivalence between supervisory sealing and self-authored sealing unconditionally - relying on the formal direction-and-control relationship as sufficient - or must Engineer B demonstrate that supervisory engagement was substantive enough to produce a level of technical confidence in the document's accuracy that approximates what personal preparation would provide?