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 a prior ruling addressing similar issues of sealing plans not personally prepared by the sealing engineer, then clarified/modified its original literal interpretation to align with prevailing engineering practices.

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.

The Board's approval of Engineer B's practice rests on extending the traditional 'direction and control' standard from BER Case 86-2 into the CADD context, implicitly treating the software as a drafting instrument rather than a substitute for supervisory judgment. However, the Board did not specify what level of substantive review (spot-checking, design-basis verification, output validation) is required to distinguish genuine direction and control from nominal oversight of a high-volume automated process. As CADD systems increase the sheer volume of output that can be produced by subordinates, the practical feasibility of item-by-item review diminishes, creating tension between the traditional review standard and modern production capacity that the Board's conclusion does not resolve.

The Board's finding that Engineer A ethically sealed documents he prepared using CADD implicitly assumes that proficiency with the software tool is separable from, and subordinate to, the engineer's independent professional judgment about the underlying design. The Board did not address the risk that CADD's precision and automated defaults could create a false sense of accuracy, potentially discouraging engineers from critically evaluating outputs rather than treating the software as authoritative. This suggests an unstated boundary: CADD competence must never substitute for engineering judgment, only assist in its execution, and Engineer A's ethical compliance depends on this distinction being maintained in practice, not merely on his sealing authority as author of the work.

Comparing the two conclusions together reveals an implicit gradation in the Board's reasoning: Engineer A, as personal author, satisfies his sealing duty through direct authorship and firsthand knowledge of the work, while Engineer B, as supervisor of others' CADD output, satisfies the same duty through a different mechanism, namely delegated but actively exercised direction and control. The Board treats both as ethically equivalent paths to fulfilling the sealing obligation, but does not clarify whether the depth of verification owed to the public is truly identical in both cases, or whether Engineer B bears a heightened duty to compensate for his lack of personal authorship through more rigorous procedural safeguards, documentation, or spot-verification of subordinate work.

Responding to Q101, meaningful 'direction and control' by Engineer B requires more than final signature review; it implies active engagement throughout the design process, such as setting design criteria, reviewing intermediate outputs, checking assumptions and default parameters used by the CADD system, and verifying that the final documents reflect sound engineering judgment. Nominal oversight limited to a cursory glance at finished plans would not satisfy the professional responsibility Engineer B assumes by sealing the work of others.

Regarding Q103, although the Board's finding does not require formal documentation, sound practice would counsel Engineer B to maintain some record of review activity (e.g., markups, design checklists, or supervisory notes) to demonstrate after the fact that direction and control was substantively exercised. Absent such evidence, Engineer B's ethical compliance rests on the presumption of professional integrity rather than on an auditable trail, which could be problematic if the propriety of the sealing is later challenged.

On Q104, the automation and apparent precision of CADD systems can create a false sense of accuracy, tempting engineers to defer to computer-generated results rather than applying independent critical judgment. The Board's conclusions implicitly assume that professional judgment remains primary and that CADD is merely a drafting tool; if engineers instead treat CADD outputs as self-validating, this would undermine the ethical basis for permitting CADD-based sealing at all.

In response to Q301, from a deontological standpoint Engineer A satisfies his duty of personal accountability because he himself prepared the documents; the CADD system is simply an instrument of his own labor, comparable to a straightedge or slide rule in earlier eras. The duty to seal only work one has personally executed and stands behind is fulfilled regardless of the technological means used to produce that work.

Addressing Q302, from a consequentialist view the ethical justification for Engineer B's practice rests on the outcome: competently produced, appropriately reviewed engineering documents that protect public safety and welfare. If direction and control over CADD operators reliably yields the same quality outcome as personal execution, then requiring Engineer B to personally perform every task would add no protective value and would be an inefficient, unjustified burden inconsistent with modern practice.

Concerning Q303, Engineer B's conduct reflects the virtue of professional integrity because he does not merely delegate blindly; he takes full responsibility for supervised work as an expression of trustworthiness and prudence, even though he did not author every detail personally. His willingness to answer for the work product, backed by direction and control, embodies the virtue-ethics ideal of accountability without requiring literal authorship of each document.

In response to Q401, if Engineer B lacked genuine direction and control over the CADD operators, the Board's ethical approval would likely not extend to him, since the underlying justification for permitting him to seal others' work depends entirely on his supervisory relationship establishing accountability equivalent to personal preparation. Without that control, sealing the work would resemble improper certification of unreviewed or unsupervised output, contrary to II.2.b. and II.2.c.

Regarding Q402, even if detailed element-by-element review were feasible, the Board's finding would likely still hold because the ethical standard turns on whether direction and control were meaningfully exercised, not on the volume or granularity of review performed. Feasibility of exhaustive review might raise the bar for what 'meaningful' direction and control looks like, but it would not change the underlying principle that supervisory responsibility, not personal drafting, is what legitimizes Engineer B's seal.

On Q403, if Engineer A had merely directed CADD operators rather than personally preparing the documents, his situation would effectively become identical to Engineer B's, and the Board's separate conclusion about Engineer A specifically as the preparer would no longer apply to him in that capacity; instead, he would need to satisfy the direction-and-control standard articulated for Engineer B to ethically seal the work.

The Board resolved the tension between Responsible Charge in CADD Work and the practical infeasibility of item-by-item review by allowing 'direction and control' to serve as the operative standard of responsible charge, rather than requiring literal, exhaustive verification of every CADD-generated element. This effectively subordinates a strict, traditional notion of Review Adequacy to a more functional standard of supervisory competence, reflecting the Code's need for Practicability in the CADD Era. The implicit message is that as production volume and automation increase, the professional standard shifts from personal verification of content to verification of process and supervisory structure.

The case demonstrates that Professional Accountability in CADD Sealing and Responsible Charge in CADD Work are not competing principles but parallel routes to the same ethical end: ensuring that a signature and seal reflect genuine professional responsibility. Engineer A satisfies this duty through personal authorship and direct command of the CADD tool, while Engineer B satisfies it through supervisory control over others' CADD work. The Board's parallel approval of both models shows that the Code does not mandate a single method of achieving accountability, but instead permits differentiated pathways—direct preparation or direction and control—so long as one of them is genuinely exercised.

Competence in CADD Proficiency is ethically subordinate to Professional Judgment Primacy in CADD Use: the Board's approval of CADD-based practice implies that skill with the software is a necessary but not sufficient condition for ethical sealing. Engineers must treat CADD output as a tool-generated draft subject to independent professional evaluation, not as a self-validating result. This prioritization protects against the risk that automation and precision in CADD systems could substitute for, rather than support, the engineer's own critical judgment—preserving the primacy of human professional responsibility over technological convenience.

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?

What specific level of review or verification must Engineer B perform on CADD-generated documents produced by others to genuinely constitute 'direction and control' rather than mere nominal oversight?

Does an engineer's proficiency with a CADD tool need to include understanding of the software's underlying algorithms and default settings, or is competence limited to interpreting and validating the outputs?

What documentation or process safeguards should exist to demonstrate, after the fact, that Engineer B actually exercised meaningful direction and control over CADD operators rather than simply signing what was produced?

Could the precision and automation offered by CADD systems create a false sense of accuracy that discourages engineers from exercising independent critical judgment on the design itself?

How should Responsible Charge in CADD Work be balanced against the practical Detailed Review Infeasibility when large volumes of CADD-generated documents make item-by-item verification by Engineer B extremely difficult?

Does Competence in CADD Proficiency risk conflicting with Professional Judgment Primacy in CADD Use if engineers begin to trust the software's default outputs over their own independent analysis?

How should Code Practicability in CADD Era be reconciled with Review Adequacy for Sealed CADD Documents when strict literal application of traditional review standards may be impossible given modern CADD production volumes?

How should Professional Accountability in CADD Sealing for Engineer A, who personally prepares his work, be differentiated from Responsible Charge in CADD Work for Engineer B, who seals the work of others, in terms of the depth of personal verification each owes the public?

From a deontological perspective, did Engineer A fulfill his duty of personal accountability by signing and sealing documents he himself prepared using a CADD system, regardless of the tool used?

From a consequentialist perspective, did the outcome of producing accurate, competently reviewed engineering documents justify Engineer B's practice of sealing CADD work performed by subordinates under his direction and control, rather than requiring him to personally execute every detail?

Did Engineer B act with professional integrity, in the virtue-ethics sense, when he signed and sealed documents produced by others under his supervision rather than personally preparing them, given that his professional judgment and oversight substituted for direct authorship?

Did Engineer A act with professional integrity when relying on CADD tool proficiency rather than manual drafting competence to prepare the documents he sealed?

If Engineer B had not maintained direction and control over the CADD operators who produced the documents, would the Board still have found it ethical for him to sign and seal their work?

If a detailed, element-by-element review of the CADD-generated output had in fact been feasible (rather than infeasible), would the Board's finding that general direction and control satisfies Engineer B's sealing duty still hold?

If Engineer A had not personally prepared the documents but had instead merely directed CADD operators as Engineer B did, would the Board's conclusion regarding Engineer A's sealing authority still apply to him?

Because this ruling arose from a chief engineer sealing work without detailed review, the Board's literal, letter-of-the-code reading (guided by the Direction and Control Principle) effectively sanctioned that practice, and it is precisely this permissive literalism that provoked the downstream Community Controversy over whether such sealing truly respects engineers' responsibility for their work product.

Responding to the controversy the literal ruling caused, this clarification leans on Consonance with Prevailing Practice to recalibrate the Board's position toward accepted industry norms, thereby setting up the more general Standard Application Ruling that follows and showing that normative legitimacy here depends on aligning with what the profession actually does rather than a bare textual reading.

As the culmination of the causal chain from controversy through clarification, this ruling is guided jointly by Full Responsibility for Work Product and Consonance with Prevailing Practice, and it fulfills or violates nothing itself because its normative role is to institutionalize a balanced standard rather than to perform an act that could itself breach or satisfy a duty.

Triggered by Technological Evolution that lets an engineer directly manage complex specialized work, signing and sealing one's own work fulfills the Direction and Control Obligation and Competence Obligation precisely because the engineer retains firsthand mastery and oversight, which is why no violation results despite the increased technical complexity.

Also driven by Technological Evolution but attributed to a different engineer who relies on subordinates, this action fulfills the Direction and Control Obligation and Review and Checking Obligation because proper supervision and review substitute for direct authorship, showing that Full Responsibility for Work Product can be satisfied through diligent oversight rather than personal execution alone.

The question arose because new CADD technology introduced doubt about whether traditional sealing standards, built for manual preparation, still adequately capture personal responsibility when tools automate significant portions of document production.

The question arose because new CADD technology separates document production from the sealing engineer's hands on labor, forcing the Board to decide whether traditional review based sealing standards still apply or whether supervisory responsibility suffices.

The question arose because CADD technology let operators generate large volumes of work under Engineer B's nominal supervision, and the code's existing direction and control language does not specify what concrete verification actions are required to make that oversight substantive rather than a rubber stamp.

As CADD systems became standard and their internal complexity grew, the traditional expectation that engineers fully understand their tools collided with the practical reality that engineers increasingly depend on software they did not build, forcing the Board to clarify what proficiency actually requires.

Because CADD workflows separate document production from the sealing engineer's direct labor, the Board and profession need after-the-fact proof that direction and control were real rather than nominal, and no established documentation standard yet exists to distinguish genuine oversight from rubber-stamping.

The question arises because CADD systems' apparent precision blurs the line between mechanical accuracy and engineering judgment, creating doubt about whether engineers are still fulfilling their duty of independent critical review or merely deferring to tool output.

The question arose because Technological Evolution in CADD production created a Detailed Review Infeasibility that exposes a gap between the letter of Engineer B's traditional review obligations and what is practically achievable, forcing a reconsideration of what Responsible Charge in CADD Work actually requires.

The question arises because CADD tools were meant to support competence, but their sophistication creates a risk that engineers substitute software trust for the independent judgment that sealing accountability requires.

The question arose because CADD production volumes created a practical gap between what full literal review would require and what is achievable, forcing the Board to reconcile code practicability with the principle of adequate review under modern technological constraints.

The question arises because CADD technology blurs the line between personally producing work and merely directing others who produce it, forcing the Board to decide whether sealing under Direction and Control can ever demand the same depth of personal verification as sealing one's own work.

The question arises because new CADD technology changes how documents are produced, creating uncertainty over whether traditional deontological accountability standards tied to manual preparation still hold when a tool mediates the engineer's own work.

The question arises because a consequentialist framing asks whether the good outcome (accurate documents) retroactively validates a practice that a rule based warrant (personal review and sealing) would otherwise question, exposing a clash between outcome focused and duty focused justifications.

The question arises because CADD technology decoupled personal authorship from sealing, forcing a reexamination of whether virtue-based integrity can be satisfied through supervisory judgment rather than direct preparation.

The question arises because Technological Evolution introduced CADD as a new mode of document preparation, creating ambiguity over whether traditional competence standards for sealing still apply when the engineer's skill is primarily in operating software rather than manual drafting or design verification.

The question arises because the Board's approval was explicitly grounded in Engineer B maintaining direction and control, so removing that condition tests whether the ethical conclusion depends on that specific warrant or on a broader responsibility principle that survives its absence.

The question arises because the Board's ruling was explicitly conditioned on the impracticality of detailed review, so removing that condition tests whether the underlying principle was direction and control as a standalone standard or merely a practical substitute adopted due to infeasibility.

The question arises because the Board's ruling for Engineer A was tied specifically to his personal preparation of the documents, and readers naturally ask whether the same favorable conclusion would hold if he instead relied on CADD operators like Engineer B, exposing a gap between authorship-based and supervision-based warrants for sealing authority.

Because Engineer A authored the documents himself and used CADD only as a production tool, the Board concluded his sealing was ethical, treating the software as equivalent to traditional drafting instruments rather than a displacement of his own engineering judgment.

Given that Engineer B retained direction and control over the operators producing the CADD documents, the Board extended the BER 86-2 supervisory standard to this context and found his sealing ethical, since responsible oversight substituted for direct authorship.

Because the Board approved Engineer B's practice without articulating what substantive review is required, and because CADD's high output volume makes exhaustive review impractical, this conclusion frames the ruling as leaving open a tension between traditional review standards and modern production capacity.

Since the Board's approval of Engineer A assumed that his tool proficiency was subordinate to his professional judgment, this conclusion reasons that his ethical compliance depends on maintaining that distinction in practice, a boundary the Board left unstated but implied.

Given that Engineer A authored his own work while Engineer B supervised others' work under direction and control, the Board implicitly ranked both as valid but distinct routes to fulfilling the sealing duty, leaving open whether Engineer B's lack of personal authorship demands additional procedural safeguards.

Given that Engineer B did not personally produce the documents, the Board concluded that his sealing duty required more than nominal sign-off, because the professional responsibility attached to sealing others' work presumes active involvement sufficient to verify sound engineering judgment underlies the final product.

Because the Board did not require formal documentation as a condition of ethical compliance, it concluded that sound practice, not obligation, counsels keeping markups or checklists, since without such records Engineer B's compliance depends solely on an unverifiable presumption of integrity.

Recognizing that CADD's apparent precision could tempt engineers toward complacency, the Board concluded that ethical use of CADD depends on preserving professional judgment as primary, since treating computer outputs as self-validating would erode the very justification for permitting CADD-based sealing.

Since Engineer A personally prepared the documents using CADD as his own working tool, the Board concluded that his duty of personal accountability was fully satisfied, treating the CADD system as functionally equivalent to earlier manual drafting instruments rather than as a substitute for his own labor.

Because Engineer B maintained direction and control that reliably yielded competently reviewed documents, the Board concluded that the outcome justified his practice, reasoning that demanding personal execution of every detail would impose an unjustified burden without improving public protection.

Given that Engineer B accepted full responsibility for work performed under his real direction and control, the board concluded his conduct exemplified professional integrity because accountability, not literal authorship, is what virtue ethics demands of a supervising engineer.

Because the ethical permission to seal others' work rests entirely on Engineer B's supervisory relationship, the board reasoned that stripping away genuine direction and control would remove the justification and make the sealing improper under II.2.b and II.2.c.

Even supposing exhaustive review were practicable, the board reasoned that supervisory responsibility rather than personal drafting legitimizes the seal, so feasibility only affects the rigor expected of that supervision, not the underlying standard itself.

Because the ethical duty attaches to the function performed rather than the individual, the board reasoned that if Engineer A instead merely directed CADD operators, he would need to satisfy the direction-and-control standard applicable to Engineer B rather than the personal-preparation standard originally applied to him.

Faced with the infeasibility of exhaustive review in high-volume CADD production, the board resolved the tension by treating meaningful direction and control as satisfying responsible charge, signaling that as automation increases, the professional standard shifts from verifying content to verifying process and supervision.

Given that Engineer A personally prepared his sealed documents and Engineer B genuinely supervised the CADD operators whose work he sealed, the Board concluded that each satisfied the same accountability duty through a different but equally valid route, so both practices were approved as ethical without requiring a single uniform method of sealing.

Given that CADD tools can produce output that appears authoritative simply because it is precise and automated, the Board concluded that competence in using the software must remain secondary to the engineer's own professional judgment, so that ease or volume of CADD production never excuses replacing independent evaluation with blind reliance on the tool.

Should Engineer A sign and seal the CADD-generated documents he personally prepared?

Should Engineer B sign and seal CADD documents prepared by others under his direction and control?

What depth of review must Engineer B perform on CADD-generated documents to genuinely exercise direction and control?

Should the Board interpret the sealing code provision literally or recalibrate its ruling to align with prevailing professional practice?

Must an engineer's CADD competence include understanding the software's underlying algorithms, or is competence satisfied by validating outputs through independent professional judgment?