Step 4: Review

Engineers shall avoid the use of statements containing a material misrepresentation of fact or omitting a material fact.

Engineers shall conform with state registration laws in the practice of engineering.

Engineers shall give credit for engineering work to those to whom credit is due, and will recognize the proprietary interests of others.

The Board cited this case to explain the purpose of Section III.8.a., which is to give the original engineer an opportunity to explain design decisions before another engineer reviews the work, though it acknowledged the facts differ since Engineer A here was discharged.

Engineer B was not unethical in performing services for the client without first notifying Engineer A.

Engineer B was unethical in making changes on specific sheets of a set of drawings without clearly indicating those changes.

Engineer B was unethical in failing to note his assumption of full responsibility for the entire set of drawings.

Beyond finding that Engineer B failed to clearly indicate his changes, the Board's reasoning implies a more serious registration-law concern: because Engineer A's seal remains intact on a document set that now contains substantial unsealed changes by Engineer B, no single seal on the public improvement plans accurately certifies who is in responsible charge of the work as a whole. This creates a misleading impression that Engineer A reviewed and approved a design he never saw, exposing contractors, inspectors, and future owners to plans whose authorship and responsibility cannot be reliably determined from the documents themselves.

The Board's finding that Engineer B was unethical for failing to note his assumption of full responsibility can be extended by observing that his vague 'revisions' notation did not merely omit detail — it created two simultaneous and inconsistent claims of responsible charge over the same set of drawings: Engineer A's still-visible seal implying original authorship and approval, and Engineer B's unspecified 'revisions' notation implying some undefined scope of authorship. This dual attribution is arguably worse than silence, because it actively obscures rather than merely fails to clarify who is accountable for which portions of the design.

While the Board correctly held that Engineer B was not obligated to notify Engineer A before accepting the assignment, this compliance finding should not be read as excusing Engineer B from independently acknowledging Engineer A's original authorship in the final documents. The absence of a notification duty toward a discharged predecessor is a separate ethical question from the duty of honest attribution owed to anyone who relies on the sealed plans; satisfying the former does not discharge the latter, and Engineer B's failure to reconcile these two obligations left the attribution problem effectively unaddressed.

Responding to Q101: Yes. By leaving Engineer A's seal and signature intact on grading and public improvement plans that had been substantially redesigned, Engineer B created a misleading representation that Engineer A was professionally responsible for or endorsed a design he never saw. This is consistent with the Board's finding in Conclusion 3 that Engineer B failed to note his assumption of responsibility for the entire set of drawings, and it independently raises a misrepresentation concern under the Code's prohibition on statements omitting material facts.

Responding to Q102: The case facts support finding a registration/sealing problem distinct from the Board's ethics-based conclusions. Because Engineer A's seal remains on record for the entire set while Engineer B made major unsealed changes to grading, drainage, sewer, and utility design, no single seal on the circulating document accurately reflects who exercised responsible charge over the finished product. This creates a de facto violation of state registration and sealing requirements, even though the Board's conclusions were framed only in terms of professional ethics violations.

Responding to Q103: Third parties such as contractors, plan-check reviewers, and future owners who rely on the sealed plans have no way to distinguish Engineer A's original design decisions from Engineer B's undocumented modifications to housing pad elevations, street routing, storm drains, and utilities. This ambiguity creates a genuine public safety risk, since field personnel could reasonably assume the entire package reflects Engineer A's sealed and verified design when critical portions were never reviewed or sealed by him at all.

Responding to Q201: There is little real tension here. The Board's acceptance of Peer Review Without Notification concerns only the threshold question of whether Engineer B needed Engineer A's permission to take the assignment; it does not excuse Engineer B from independently and fully understanding the original design once he possessed the drawings. Engineer B's failure to attribute and document specific changes reflects a separate breakdown in diligence and honesty, not a necessary consequence of skipping notification.

Responding to Q203: Yes, a genuine conflict existed. By leaving Engineer A's seal in place while simultaneously placing a note claiming responsibility for unspecified 'revisions,' Engineer B created two overlapping and inconsistent claims of responsible charge over the same set of drawings. Proper resolution required either removing or superseding Engineer A's seal on affected sheets, or precisely delineating which sheets and elements fell under Engineer B's new responsibility, so that responsible charge was unambiguous rather than dually claimed.

Responding to Q301: From a deontological standpoint, Engineer B had a duty grounded in honesty and professional transparency to clearly notate every change made to Engineer A's sealed drawings. This duty is not contingent on whether any harm actually resulted; it exists because accurate documentation of design responsibility is a categorical professional obligation. Engineer B's vague notation and unmarked changes therefore constitute a duty-based failure independent of consequences.

Responding to Q303: Engineer B did not act with full professional integrity. Adding a vague note claiming responsibility for undefined 'revisions' while leaving Engineer A's seal and signature untouched on plans that had been substantially redesigned reflects an attempt to claim some credit or protection without accepting the corresponding transparency obligations that should accompany that claim. Integrity would have required either a complete and specific accounting of changes or formal removal/supersession of Engineer A's seal.

Responding to Q304: Yes. Once Engineer B undertook substantive redesign of Engineer A's plans, an independent deontological duty arose to assume and document full responsibility for the entire modified set, separate and apart from any question of whether he needed to notify Engineer A beforehand. The duty to fully own the revised work product follows from the act of substantially altering sealed engineering documents, not from the notification question addressed in Conclusion 1.

Responding to Q402: The violation regarding failure to clearly notate changes would very likely still stand even if Engineer B had removed Engineer A's seal before making changes. The Board's Conclusion 2 rests on Engineer B's failure to clearly indicate which specific changes he made on specific sheets, an omission that exists independently of whose seal appears on the documents. Removing Engineer A's seal would have mitigated the misrepresentation concern under Q101, but would not itself have cured the lack of clear, sheet-by-sheet identification of the modifications.

Responding to Q403: Had Engineer B's note specifically identified which sheets and elements he was taking responsibility for, the Board likely would not have found him unethical under Conclusion 3, since the core defect was the vagueness of the notation rather than the mere act of adding a note. A precise, sheet-specific statement of assumed responsibility would have satisfied the underlying obligation to make clear the scope of design accountability, even if Engineer A's seal remained visible elsewhere on the document.

The Board resolved the tension between Peer Review Without Notification and Work Attribution in Redesign by treating them as independent duties rather than substitutes for one another: Engineer B's freedom to accept the assignment without contacting Engineer A did not relieve him of a separate, non-negotiable duty to document and attribute the changes he made. This shows that procedural permissions (who may be consulted before work begins) and substantive honesty obligations (how work must be disclosed once performed) operate on different ethical tracks, and satisfying one does not satisfy the other.

The conflict between Responsible Charge over Sealed Plans and Accountability for Full Design was left unresolved by Engineer B's conduct, and the Board's findings effectively prioritize sealed-plan integrity as the dominant principle: leaving Engineer A's seal intact while making substantial unsealed changes created two simultaneous but inconsistent claims of responsible charge, which the Code cannot tolerate. This suggests that in redesign work, the seal itself functions as a legal and ethical representation of exclusive responsibility, so any modification by a second engineer must either formally supersede the original seal or be so clearly bounded that the two zones of responsibility remain legally distinguishable.

Honesty in Plan Revision Notation was subordinated to a generic, self-serving assertion of 'responsibility for revisions,' revealing that vague attribution statements cannot satisfy the underlying purpose of Work Attribution in Redesign, which is to make clear to third parties exactly which portions of a mixed-authorship document reflect whose engineering judgment. The case teaches that when these two principles are in tension, specificity of notation must take priority over mere acknowledgment of involvement, because an unspecific claim of responsibility can be as misleading as no claim at all.

Was Engineer B unethical in performing services for the client without notifying Engineer A?

Was Engineer B unethical in making changes on specific sheets of a set of drawings without clearly identifying those changes?

Was Engineer B unethical in failing to note his assumption of responsibility for the entire set of drawings?

By leaving Engineer A's seal and signature intact on plans that were substantially redesigned, did Engineer B create a misleading impression that Engineer A was responsible for or endorsed the final design, even though Engineer A had no involvement in or knowledge of the changes?

Does a registration/sealing law violation arise from the fact that a set of drawings now in circulation contains substantial unsealed engineering changes by Engineer B alongside Engineer A's original seal, such that no single seal accurately represents responsible charge over the whole set?

What is the risk to public safety and third parties (contractors, inspectors, future owners) who rely on the plans when they cannot tell which portions reflect Engineer A's original design versus Engineer B's undocumented revisions?

Should the client bear any responsibility for providing Engineer B with a signed and sealed set of another engineer's plans to use as a redesign template, rather than requiring a clean-sheet approach or requiring Engineer B to formally supersede the prior seal?

Does the principle of Peer Review Without Notification (permitting Engineer B to accept the assignment without contacting Engineer A) conflict with Accountability for Full Design, since proceeding without consultation may have made it harder for Engineer B to fully understand and properly attribute the scope of changes needed?

How should Honesty in Plan Revision Notation be balanced against Work Attribution in Redesign when a vague note claiming responsibility for 'revisions' is used instead of clearly delineating which specific sheets, dimensions, or design elements were changed?

Does Responsible Charge over Sealed Plans conflict with Accountability for Full Design when Engineer B leaves Engineer A's seal intact while simultaneously claiming responsibility for 'revisions,' effectively creating dual and inconsistent claims of responsible charge over the same document set?

How should the principle permitting Peer Review Without Notification be reconciled with Work Attribution in Redesign, given that proper attribution arguably requires some acknowledgment of the original engineer's role even if prior notification is not ethically mandatory?

From a deontological perspective, did Engineer B fulfill his duty to clearly and honestly notate all changes made to Engineer A's sealed drawings, regardless of the consequences of doing so?

Did the absence of any reported harm to the client or public from Engineer B's undocumented revisions justify treating the failure to notate changes as a merely technical, rather than substantive, ethical lapse?

Did Engineer B act with professional integrity when he added a vague note claiming responsibility for 'revisions' while leaving Engineer A's seal and signature intact on plans that had been substantially redesigned?

From a deontological standpoint, did Engineer B owe an independent duty to assume full responsibility for the entire set of drawings once he modified them, separate from any duty regarding notification of Engineer A?

If Engineer A had still been actively retained by the client (rather than having been discharged) when Engineer B was engaged to review and redesign the project, would the Board still have concluded that Engineer B was not unethical in proceeding without notifying Engineer A?

If Engineer B had removed Engineer A's seal and signature from the public improvement plans before making his changes, rather than leaving them intact, would the Board still have found the same violation regarding failure to clearly notate changes?

If Engineer B's note on the title sheet had specified exactly which sheets and elements he was taking responsibility for, rather than generically referencing 'revisions of the plans,' would the Board still have found him unethical for failing to note assumption of responsibility for the entire set of drawings?

Engineer Discharge, though carrying no explicit fulfillment or violation, is the pivotal event that converts client dissatisfaction into a formal termination of the professional relationship, which is what makes the later transfer of drawings and retention of a successor engineer normatively relevant.

Original Drawings Transfer carries no normative edges and is not tied to any downstream causal chain, indicating it functions merely as a neutral administrative step that enables continuity of the project rather than raising an ethical duty itself.

Successor Engineer Retention has no direct fulfillment or violation attached, but it creates the Residual Work Connection that obligates the new engineer to engage responsibly with the prior engineer's work, setting up the context in which later consultation obligations become relevant.

Review Engagement Acceptance itself is normatively neutral, yet it is the action that directly produces the Consultation Omission, meaning that accepting the review without safeguards effectively enables a downstream ethical failure attributable to Engineer B.

Consultation Omission is guided by the Professional Courtesy in Review provision, so failing to consult the original engineer before reviewing the plans undermines the courtesy norm meant to prevent misunderstandings, especially given that the plans already contain undocumented modifications that make them misleading and thus more in need of clarification through consultation.

Because Engineer B sealed the plans and thereby accepted design responsibility under Section III.9, this act of acknowledgment set the baseline of accountability against which the later undocumented changes and vague notation would be judged as breaches rather than mere oversights.

Modifying the grading plan without documentation violates the duty to note design changes and undermines the very responsibility Engineer B had acknowledged, and this omission is what causally produces the misleading condition of the plans that later confuses the successor's review.

Leaving utility design changes unrecorded breaches the same documentation duty and responsibility acknowledgment, and it independently contributes to the plans becoming misleading, compounding the risk created by the undocumented grading change.

Using a vague responsibility notation instead of clearly documenting who was accountable violates both the duty to note changes and the acknowledgment of design responsibility, and this vagueness is precisely what renders the notation meaningless and prevents the successor engineer from relying on it to understand the plan's history.

The question arises because Engineer B's silent takeover of Engineer A's discharged work creates ambiguity over whether professional courtesy obligations survive a client-initiated termination.

The question arises because Engineer B modified sealed drawings originally created by Engineer A without clearly marking which specific changes were made, creating ambiguity about whether a general acknowledgment of responsibility satisfies the Code's more specific requirement to note each design change.

The question arises because Engineer B's vague notation created ambiguity about whether his seal implied full accountability or only accountability for the noted changes, exposing a gap between what the Code requires in notation practice and what sealing conventionally implies.

The question arises because the physical artifact (the plans) retained a signal of Engineer A's involvement (the seal) even though the substantive facts (undocumented revisions, no communication) no longer matched that signal, creating an interpretive gap between what the document implies and what actually occurred.

The question arises because the physical artifact, a single drawing set with mixed authorship and only one seal, creates ambiguity about whose seal governs what content, forcing a judgment about whether registration law requires perfect seal-to-content correspondence or merely honest attribution of changes.

The question arises because the undocumented and vaguely notated revisions sever the normal chain of traceable responsibility that contractors, inspectors, and future owners rely on to assess design intent and accountability, creating a safety risk that neither engineer's individual warrant fully resolves.

The question arises because the client's practical decision to transfer an already sealed design as a working template sits upstream of Engineer B's documented failures, prompting scrutiny of whether an ostensibly non-engineer party's procurement choice contributed to a professional lapse that codes of ethics assign squarely to the licensed engineer.

The question arises because the Code permits engineers to review prior work without notifying the original engineer, yet this very lack of contact is causally linked to the undocumented and vaguely attributed revisions that followed, creating doubt about whether the no notification norm undermines the accountability norm in cases of design succession.

The question arises because Engineer B's notation technically discloses that revisions occurred (satisfying a bare honesty warrant) while simultaneously withholding the specificity needed to attribute responsibility for particular design elements, creating a genuine conflict between two plausible readings of the same disclosure obligation.

The question arises because Engineer B's action of retaining Engineer A's seal alongside undocumented and vaguely noted changes creates an ambiguous division of responsible charge, making it unclear which engineer bears accountability for the resulting code violations.

The question arose because the case data shows Engineer B both reviewing without notifying Engineer A and revising the plans without clearly noting what was changed or by whom, forcing a reconciliation of two principles (Peer Review Without Notification and Work Attribution in Redesign) that address different obligations but touch the same underlying relationship between the two engineers.

The question arises because Engineer B's notation created ambiguity, satisfying a general attribution obligation while seemingly violating a more specific honesty obligation, so a deontological lens is needed to determine which duty takes precedence irrespective of the resulting client dissatisfaction.

The question arises because Engineer B's undocumented changes satisfy the factual conditions of a code violation, yet the absence of reported harm creates competing standards for judging whether the violation is serious or trivial.

The question arises because a single ambiguous action, a vague note plus intact original seal, can be read either as adequate disclosure or as a deceptive half measure, and the extent of undocumented changes determines which interpretation the ethical code supports.

The question arises because the Undocumented Plan Revisions and Vague Responsibility Notation leave it unclear whether Engineer B's ethical exposure is limited to the specific changes he failed to document or extends deontologically to the whole set of drawings he touched and sealed.

This question arose because the Board's ruling rested on the specific fact of Engineer A's discharge, and changing that single data point tests whether the warrant justifying non-notification depended on discharge status or would extend to active retention as well.

The question arises because the case facts conflate two distinct professional duties, honest attribution via the seal and clear notation of changes, and it is unclear whether the Board's violation finding depended on the seal condition or would persist under any authorship configuration.

The question arises because the Board's finding conflated two distinct duties, the duty to note specific changes and the duty to accept responsibility for the whole sealed document, leaving open whether better notation practice alone could have resolved the ethical violation or whether the seal-based obligation is independent of notation quality.

Given that Engineer A had already been terminated by the client before Engineer B's engagement, the Board concluded that no duty of prior notification arose, because the peer review notification norm presumes an ongoing engineering relationship that no longer existed here.

Because Engineer B altered grading and utility elements on specific sheets without marking or otherwise flagging those changes, the Board concluded this omission violated the duty of honest notation, since third parties reviewing the plans could not distinguish original from revised work.

Given that Engineer B's notation was limited to vague 'revisions' language without specifying which parts of the drawing set he now owned professionally, the Board concluded he failed to fulfill the duty to assume full responsibility for the entire modified set.

Because Engineer A's seal remained on a plan set that had been substantially altered without corresponding seal changes, the Board reasoned that this created a document whose certification no longer matched reality, implicating registration-law compliance beyond mere notation etiquette.

Given that Engineer B's imprecise notation sat alongside Engineer A's still-visible seal, the Board reasoned that this combination produced two competing and unresolved claims of authorship, making the document more misleading than if Engineer B had left no notation at all.

Given that Engineer A was already discharged when Engineer B was retained, the Board found no notification duty was breached, but because Engineer B still failed to name Engineer A as original author, the Board concluded that compliance with the notification norm did not resolve the separate attribution failure.

Because Engineer A's seal stayed on plans that had been substantially reworked without his knowledge, the Board concluded this created a misleading impression of his endorsement, reinforcing its separate finding that Engineer B never clarified his own scope of responsibility.

Given that Engineer A's seal covers the whole package while major technical elements were altered and left unsealed by Engineer B, the analysis concludes a de facto registration violation exists alongside, but distinct from, the Board's ethics findings.

Because critical grading, drainage, and utility elements were changed without documentation while Engineer A's seal remained, the analysis concludes that third parties relying on the plans face a real safety risk from being unable to tell whose design controls which portion.

Since Engineer B had the complete original drawings in hand after accepting the assignment, the Board reasons that his failure to attribute and document changes cannot be excused as a necessary consequence of not notifying Engineer A, treating the two duties as largely non-conflicting.

Given that Engineer A's seal remained on the drawings and Engineer B added only a vague revisions note without removing that seal or specifying scope, the board concluded a genuine conflict existed because the drawings simultaneously implied two different engineers held responsible charge over the same work.

Given that Engineer B altered sealed drawings but only vaguely referenced 'revisions,' the board concluded a duty-based failure occurred because the obligation to clearly document changes is categorical and does not depend on whether any actual harm followed from the omission.

Given that Engineer B's note asserted some responsibility without full transparency and left Engineer A's seal in place despite substantial redesign, the board concluded this reflected an attempt to gain partial credit or protection without accepting the corresponding disclosure obligations, falling short of full professional integrity.

Given that Engineer B substantially redesigned Engineer A's plans, the board concluded an independent duty to assume and document full responsibility for the entire modified set arose from that act of substantive alteration itself, distinct from any separate finding about notification.

Given that the notation violation rested on the lack of sheet-specific identification of changes rather than on the presence of Engineer A's seal, the board concluded that even a counterfactual removal of that seal would very likely not have cured the separate failure to clearly document which changes were made and where.

Given that the actual violation stemmed from vagueness rather than from adding a note at all, the Board reasoned that a sheet-specific statement of assumed responsibility would have discharged Engineer B's disclosure duty even though Engineer A's seal was still present elsewhere on the plans.

Because Engineer B's freedom to accept the assignment without contacting Engineer A concerned only the acceptance stage, the Board concluded that this permission could not excuse the separate and non-negotiable duty to attribute the changes once the redesign work was actually performed.

Because Engineer B left Engineer A's seal untouched while introducing substantial unsealed modifications, the Board found the two simultaneous claims of responsible charge incompatible with the Code, treating the seal as the operative representation of exclusive responsibility that had not been properly transferred or bounded.

Given that Engineer B's note only generically claimed responsibility for 'revisions' while the redesign was substantial, the Board concluded that vague attribution failed the purpose of Work Attribution in Redesign, since third parties could not determine whose engineering judgment governed which portions of the mixed-authorship document.

Should Engineer B accept the client's assignment to review and redesign Engineer A's plans without notifying or consulting Engineer A, given that the client had already discharged Engineer A?

Should Engineer B itemize and specifically notate each change he made to the grading, drainage, sewer, and utility plans, or rely on a general revision note?

Should Engineer B add a notation acknowledging his responsibility for the full design of the drawing set, or limit his notation to a vague reference to unspecified revisions?

Should Engineer B formally supersede or remove Engineer A's seal and signature on substantially redesigned sheets, or leave them intact alongside his own revision note?

Should Engineer B clearly delineate which portions of the plans are Engineer A's original work versus his own redesign, or leave the plan set without such attribution?