Step 4: Full View

Entities, provisions, decisions, and narrative

Back to Case
Modification of Signed and Sealed Plans by Other Than Responsible Engineer
Step 4 of 5

185

Entities

3

Provisions

1

Precedents

18

Questions

19

Conclusions

Stalemate

Transformation
Stalemate Competing obligations remain in tension without clear resolution
The scenario does not resolve via reassignment of duty (transfer) but instead leaves Engineer A's seal-based responsibility and Engineer B's revision-based responsibility co-existing and legally unreconciled, matching the framework's stalemate pattern where stakeholders 'cannot quit the scenario' because they remain 'trapped in the set of rules' governing sealed engineering documents.
Full Entity Graph
Loading...
Context: 0 Normative: 0 Temporal: 0 Synthesis: 0
Filter:
Building graph...
Entity Types
Synthesis Reasoning Flow
Shows how NSPE provisions inform questions and conclusions - the board's reasoning chain

The board's deliberative chain: which code provisions informed which ethical questions, and how those questions were resolved. Toggle "Show Entities" to see which entities each provision applies to.

Nodes:
■ Provision (e.g., I.1.) ◆ Question: Board = board-explicit, Impl = implicit, Tens = principle tension, Theo = theoretical, CF = counterfactual ▬ Conclusion: Board = board-explicit, Resp = question response, Ext = analytical extension, Synth = principle synthesis ▬ Entity (hidden by default)
Edges:
→ informs → answered by → applies to
Provisions (3)
View Extraction

All provisions in play for this case: the union of board-stated references and analysis-found citations (see each provision's provenance badge). The OntServe case page's Cited NSPE Provisions panel shows the subset actually cited by the committed conclusions, so its count can be lower.

III.3.a board + analysis Engineers shall avoid the use of statements containing a material misrepresentation of fact or omitting a material fact.
How this applies in the case (showing 3 of 21)
Obligation
Engineer B Revision Notation Duty
Failing to note changes would omit material facts about who did what work
Action
Vague Responsibility Notation
A vague notation about responsibility omits material facts about who altered the plans
State
Intact Seal On Revised Plans
Sealing revised plans without noting changes misrepresents that the sealing engineer is responsible for the entire document
Obligation (3)
  • Engineer B Revision Notation Duty
    Failing to note changes would omit material facts about who did what work
  • Engineer B Change Notation Duty
    Not documenting changes to plans would misrepresent the true authorship of the design elements
  • Engineer B Full Design Responsibility Duty
    Not acknowledging full responsibility for fundamental changes would misrepresent the scope of his involvement
Action (3)
  • Vague Responsibility Notation
    A vague notation about responsibility omits material facts about who altered the plans
  • Undocumented Grading Plan Modification
    Failing to document the modification omits a material fact about changes to sealed plans
  • Undocumented Utility Design Changes
    Failing to document utility changes omits a material fact about alterations to sealed plans
State (3)
  • Intact Seal On Revised Plans
    Sealing revised plans without noting changes misrepresents that the sealing engineer is responsible for the entire document
  • Undocumented Plan Revisions
    Failing to document changes to sealed plans omits material facts about what was actually modified
  • Engineer B Design Impact Recognition Failure
    Not recognizing or disclosing the impact of design changes constitutes a misrepresentation by omission
Constraint (2)
  • Engineer B Undocumented Revision Deception
    Circulating plans without documenting changes omits material facts about who made the revisions
  • Engineer B Intact Seal Boundary
    Leaving Engineer A's seal intact while claiming credit misrepresents who is responsible for the work
Principle (4)
  • Accountability for Plan Revisions
    Failing to note what changes were made omits material facts about the plan revisions
  • Honesty in Plan Revision Notation
    Misleading omission of change notations constitutes a material misrepresentation by omission
  • Accountability for Full Design
    Not acknowledging responsibility for the full design omits a material fact about authorship
  • Work Attribution in Redesign
    Mixing plans without indicating whose work is whose omits material facts about the design origin
Role (1)
  • Engineer B Redesign Engineer
    Engineer B must avoid misrepresenting facts when signing and sealing revised plans containing another engineer's original work
Event (2)
  • Misleading Plans Condition
    Plans that mislead involve a material misrepresentation or omission of fact
  • Notation Rendered Meaningless
    A meaningless notation on sealed plans omits material facts about responsibility
Resource (1)
  • NSPE Code of Ethics
    Notation of design changes relates to avoiding misrepresentation of the original design intent
Capability (2)
  • Engineer B Responsibility Acceptance
    A vague responsibility note without specifics omits material facts about which work Engineer B actually performed
  • Engineer B Work Attribution
    Failing to notate specific changes to Engineer A's plans constitutes omission of material facts about authorship
III.8.a board + analysis Engineers shall conform with state registration laws in the practice of engineering.
How this applies in the case (showing 3 of 15)
Obligation
Engineer B Revision Responsibility Duty
Properly assuming responsibility for revisions aligns with state registration requirements for sealing work
Action
Undocumented Grading Plan Modification
Altering sealed plans without proper authority violates state registration laws governing sealed documents
State
Intact Seal On Revised Plans
Registration laws typically require the sealing engineer to be responsible for all sealed content including revisions
Obligation (2)
  • Engineer B Revision Responsibility Duty
    Properly assuming responsibility for revisions aligns with state registration requirements for sealing work
  • Engineer B Full Design Responsibility Duty
    Acknowledging responsibility through notations is required under state registration laws for sealed plans
Action (3)
  • Undocumented Grading Plan Modification
    Altering sealed plans without proper authority violates state registration laws governing sealed documents
  • Undocumented Utility Design Changes
    Modifying sealed engineering plans without proper registration authority violates state law
  • Plan Preparation and Sealing
    Sealing plans requires conformance with state registration laws for the engineer of record
State (3)
  • Intact Seal On Revised Plans
    Registration laws typically require the sealing engineer to be responsible for all sealed content including revisions
  • Undocumented Plan Revisions
    State registration laws require proper documentation and identification of who made specific plan changes
  • Engineer B Code Violation Finding
    Violating a code requirement directly conflicts with conforming to state registration and practice laws
Constraint (1)
  • Engineer B Intact Seal Boundary
    State registration laws require the responsible engineer to seal only the work they performed
Principle (2)
  • Responsible Charge over Sealed Plans
    State registration laws require the engineer signing and sealing plans to be in responsible charge of the design
  • Accountability for Full Design
    Registration laws require an engineer to take responsibility for the entirety of the sealed design
Role (1)
  • Engineer B Redesign Engineer
    Engineer B must conform to state registration laws regarding sealing and modifying previously sealed plans
Event (2)
  • Misleading Plans Condition
    Modifying sealed plans by someone other than the responsible engineer violates registration law requirements
  • Notation Rendered Meaningless
    Failure to properly note changes conflicts with state registration law obligations for sealed documents
Resource (1)
  • NSPE Code of Ethics
    Responsibility for design and sealing plans is governed by state registration law compliance
III.9 board + analysis Engineers shall give credit for engineering work to those to whom credit is due, and will recognize the proprietary interests of others.
How this applies in the case (showing 3 of 23)
Obligation
Engineer B Work Attribution Duty
Indicating which work belongs to Engineer A versus Engineer B directly reflects giving credit where due
Action
Undocumented Grading Plan Modification
Modifying sealed plans without credit disregards the proprietary interest of the original engineer
State
Undocumented Plan Revisions
Failing to document revisions fails to give proper credit to the engineer who actually performed that work
Obligation (3)
  • Engineer B Work Attribution Duty
    Indicating which work belongs to Engineer A versus Engineer B directly reflects giving credit where due
  • Engineer B Peer Review Notification Duty
    Notifying Engineer A recognizes his proprietary interest in the original work
  • Engineer B Revision Notation Duty
    Noting changes ensures proper credit is given to Engineer A for his original contributions
Action (4)
  • Undocumented Grading Plan Modification
    Modifying sealed plans without credit disregards the proprietary interest of the original engineer
  • Undocumented Utility Design Changes
    Changing utility designs without attribution disregards the original engineer's proprietary work
  • Consultation Omission
    Failing to consult the original engineer disregards their proprietary interest in the work
  • Original Drawings Transfer
    Transferring drawings implicates recognition of the original engineer's proprietary interest in the work
State (3)
  • Undocumented Plan Revisions
    Failing to document revisions fails to give proper credit to the engineer who actually performed that work
  • No Communications Between Engineers
    Lack of communication prevents proper recognition of each engineer's proprietary contributions to the design
  • Engineer A Post-Discharge Work Connection
    Continuing to associate with work after discharge without credit attribution raises proprietary interest concerns
Constraint (2)
  • Engineer B Intact Seal Boundary
    Proper credit requires removing or replacing the original engineer's seal when claiming responsibility for revisions
  • Engineer B Undocumented Revision Deception
    Failing to disclose modifications denies Engineer A recognition for the original work
Principle (2)
  • Work Attribution in Redesign
    Credit must be given to Engineer A for the portions of work that remained his
  • Accountability for Plan Revisions
    Proper notation of revisions recognizes the proprietary interest of the original engineer's work
Role (2)
  • Engineer B Redesign Engineer
    Engineer B must give credit to Engineer A for the original design work retained in the modified plans
  • Engineer A Original Design Engineer
    Engineer A has a proprietary interest in his original signed and sealed design work
Event (2)
  • Residual Work Connection
    Original engineer retains proprietary interest in work still connected to the project
  • Professional Relationship Termination
    Ending the relationship does not remove the need to credit and respect original engineer's work
Resource (2)
  • NSPE Code of Ethics
    Recognizing proprietary interests relates to crediting the original engineer for prior design work
  • BER Case 79-7
    This case directly addresses notifying the original engineer to recognize their proprietary interest in the work
Capability (3)
  • Engineer B Work Attribution
    This provision directly requires giving credit for engineering work and recognizing proprietary interests, matching the Board's holding
  • Engineer A Engineering Design
    Engineer A's original design work deserves credit recognition when modified by another engineer
  • Engineer B Plan Review
    Reviewing another engineer's work requires recognizing the proprietary interest in that original work
Cross-Case Connections
View Extraction
Explicit Board-Cited Precedents 1 Lineage Graph

Cases explicitly cited by the Board in this opinion. These represent direct expert judgment about intertextual relevance.

Principle Established:

The purpose of the rule against reviewing another engineer's work without notification is to allow the original engineer to provide comments or explanations for technical decisions, giving the reviewing engineer fuller understanding of the original design.

Citation Context:

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.

Relevant Excerpts
discussion: "In Case 79-7 an engineer was asked to inspect mechanical and electrical engineering work performed seven years earlier. The Board concluded that the engineer notified the former engineer..."
discussion: "While the facts of Case 79-7 are different from those in the instant case in that in the instant case the client clearly discharged Engineer A from his services, we think that many of the reasons for Section III.8.a. as stated in Case 79-7 are relevant..."
discussion: "For the reasons cited in Case 79-7 we think it would have been wiser and more professional for Engineer B to consult with Engineer A before undertaking to modify the plans prepared by Engineer A."
Implicit Similar Cases 10 Similarity Network

Cases sharing ontology classes or structural similarity. These connections arise from constrained extraction against a shared vocabulary.

Component Similarity 58% Facts Similarity 58% Discussion Similarity 46% Provision Overlap 29% Outcome Alignment 100% Tag Overlap 50%
Shared provisions: III.8.a, III.9 Same outcome unethical View Synthesis
Component Similarity 52% Facts Similarity 44% Discussion Similarity 55% Provision Overlap 33% Outcome Alignment 100% Tag Overlap 40%
Shared provisions: III.9 Same outcome unethical View Synthesis
Component Similarity 65% Facts Similarity 51% Discussion Similarity 72% Provision Overlap 14% Outcome Alignment 100% Tag Overlap 12%
Shared provisions: III.8.a Same outcome unethical View Synthesis
Component Similarity 48% Facts Similarity 52% Discussion Similarity 55% Provision Overlap 29% Outcome Alignment 100% Tag Overlap 38%
Shared provisions: III.3.a, III.8.a Same outcome unethical View Synthesis
Component Similarity 57% Facts Similarity 50% Discussion Similarity 59% Provision Overlap 12% Outcome Alignment 100% Tag Overlap 18%
Shared provisions: III.3.a Same outcome unethical View Synthesis
Component Similarity 67% Facts Similarity 65% Discussion Similarity 50% Outcome Alignment 100% Tag Overlap 9%
Same outcome unethical View Synthesis
Component Similarity 50% Facts Similarity 40% Discussion Similarity 47% Provision Overlap 17% Outcome Alignment 100% Tag Overlap 25%
Shared provisions: III.3.a Same outcome unethical View Synthesis
Component Similarity 66% Facts Similarity 60% Discussion Similarity 70% Outcome Alignment 100%
Same outcome unethical View Synthesis
Component Similarity 62% Facts Similarity 64% Discussion Similarity 45% Outcome Alignment 100% Tag Overlap 10%
Same outcome unethical View Synthesis
Component Similarity 61% Facts Similarity 54% Discussion Similarity 48% Outcome Alignment 100%
Same outcome unethical View Synthesis
Questions & Conclusions (3 board)
View Extraction
Board Board question 1

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

Board conclusion Engineer B was not unethical in performing services for the client without first notifying Engineer A.
Resolved by: The Board weighed the courtesy norm of notifying a prior engineer against the fact that no such engineer remained actively retained, and found the notification duty inapplicable once discharge had occurred. (confidence 0.75)
III.8.a. 3 principles 3 facts Conditions Narrative
Principle tension (2)

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?

AnalyticalResponding 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.
Resolved by: The Board treats the notification principle and the attribution principle as governing separate stages of conduct, finding little real tension because the latter duty survives regardless of how the former was resolved. (confidence 0.70)
III.9. 3 principles 3 facts Conditions Narrative
Also discussed in: C103

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?

AnalyticalThe 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.
Resolved by: The Board refuses to let the procedural permission to skip notification substitute for the substantive duty of honest attribution, holding that satisfying one obligation does not discharge the other. (confidence 0.70)
III.9. 3 principles 3 facts Conditions Narrative
Counterfactual (1)

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?

Board Board question 2

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

Board conclusion Engineer B was unethical in making changes on specific sheets of a set of drawings without clearly indicating those changes.
Resolved by: The Board weighed Engineer B's practical convenience in reusing the existing drawing set against the profession's honesty and attribution norms, and found the failure to mark changes outweighed any efficiency gained. (confidence 0.85)
III.3.a. III.9. 3 principles 3 facts Conditions Narrative
Implicit (1)

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?

AnalyticalResponding 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.
Resolved by: The Board balances the practical reliance interests of third parties against the incomplete documentation left by Engineer B, resolving in favor of recognizing a genuine safety risk from the ambiguity. (confidence 0.75)
III.3.a. III.8.a. 2 principles 3 facts Conditions Narrative
Also discussed in: C101
Principle tension (1)

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?

AnalyticalHonesty 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.
Resolved by: The Board prioritizes specificity of notation over the mere fact of acknowledging involvement, treating an unspecific claim of responsibility as functionally equivalent to no claim at all when the two principles conflict. (confidence 0.75)
III.3.a. III.9. 2 principles 3 facts Conditions Narrative
Theoretical (2)

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?

AnalyticalResponding 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.
Resolved by: The board subordinated any consequentialist concern about actual harm to a categorical duty of honest documentation, treating the duty as binding regardless of outcome. (confidence 0.85)
III.3.a. 2 principles 3 facts Conditions Narrative

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?

Counterfactual (1)

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?

AnalyticalResponding 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.
Resolved by: The board distinguished the misrepresentation harm tied to the intact seal from the separate documentation harm tied to unclear notation, concluding removal of the seal would resolve only the former. (confidence 0.75)
III.3.a. 2 principles 3 facts Conditions Narrative
Board Board question 3

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

Board conclusion Engineer B was unethical in failing to note his assumption of full responsibility for the entire set of drawings.
Resolved by: The Board weighed Engineer B's implicit claim of only partial responsibility (for 'revisions') against the profession's requirement that whoever modifies a sealed set must accept responsibility for the whole, resolving in favor of the latter. (confidence 0.85)
III.3.a. III.9. 3 principles 3 facts Conditions Narrative
Also discussed in: C102
Implicit (2)

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?

AnalyticalBeyond 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.
Resolved by: The Board extended its notation-based finding into a registration-law concern, weighing the convenience of leaving Engineer A's seal untouched against the statutory requirement that a seal accurately certify responsible charge, and found the latter controlling. (confidence 0.70)
III.8.a. III.3.a. 3 principles 3 facts Conditions Narrative
AnalyticalResponding 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.
Resolved by: The Board weighs the convenience of leaving an existing valid seal in place against the risk of misrepresenting authorship, and finds the misrepresentation risk controls once changes become substantial. (confidence 0.85)
III.3.a. 3 principles 3 facts Conditions Narrative

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?

AnalyticalThe 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.
Resolved by: The Board weighed the appearance of dual responsible-charge claims against the value of any partial disclosure Engineer B's notation provided, concluding the coexistence of both claims was more misleading than had he said nothing at all. (confidence 0.65)
III.3.a. III.9. 3 principles 3 facts Conditions Narrative
AnalyticalResponding 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.
Resolved by: The analysis weighs the ethics-based attribution violation already found against a distinct statutory sealing requirement, concluding both can independently apply without one subsuming the other. (confidence 0.60)
III.8.a. 2 principles 3 facts Conditions Narrative
Also discussed in: C101
Principle tension (1)

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?

AnalyticalResponding 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.
Resolved by: The board treated the retained seal and the new vague claim of responsibility as two overlapping assertions of responsible charge that could not both stand, resolving the conflict in favor of requiring unambiguous singular attribution over dual claims. (confidence 0.85)
III.8.a. III.9. 3 principles 3 facts Conditions Narrative
AnalyticalThe 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.
Resolved by: The Board effectively subordinates the claim of shared or updated accountability to the primacy of sealed-plan integrity, treating an intact seal alongside undocumented changes as an unresolvable dual claim of responsible charge rather than a balanced compromise. (confidence 0.75)
III.8.a. III.3.a. 3 principles 3 facts Conditions Narrative
Theoretical (2)

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?

AnalyticalResponding 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.
Resolved by: The board weighed the appearance of claiming credit or protection against the transparency obligations that should accompany such a claim, finding the balance tipped toward a lack of integrity because the claim was made without matching disclosure. (confidence 0.80)
III.3.a. III.9. 3 principles 3 facts Conditions Narrative

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?

AnalyticalResponding 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.
Resolved by: The board separated the duty to notify the original engineer from the duty to own the revised work product, concluding the latter arises independently from the act of substantial modification itself. (confidence 0.80)
III.9. 2 principles 3 facts Conditions Narrative
Counterfactual (1)

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?

AnalyticalResponding 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.
Resolved by: The Board treats specificity of attribution as capable of satisfying the underlying disclosure obligation even while the original engineer's seal remains present, so precision in notation outweighs the mere coexistence of two engineers' marks on one document. (confidence 0.75)
III.3.a. III.9. 3 principles 3 facts Conditions Narrative
Analytical questions (1)

Questions the analysis generates beyond the board’s explicit questions: implicit issues, principle tensions, theoretical framings, and counterfactuals. A question with an identified source board question appears nested under that question above.

Implicit (1)

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?

Decisions & Arguments (5)
View Extraction

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?

Options considered:
O1 Proceed with the review and redesign engagement relying on the client's confirmation that Engineer A was fully discharged, without contacting Engineer A. Board's choice
O2 Contact Engineer A to inform him of the new engagement before beginning any review or redesign work, even though not strictly required.
O3 Reach out to Engineer A as a professional courtesy to understand his original design rationale before modifying the plans, given his residual connection to the work.
Argument structure (Toulmin):
Grounds

The client discharged Engineer A after paying his full fee, obtained his original drawings, and then retained Engineer B, giving him Engineer A's plans as a guide; no communications occurred between the two engineers after Engineer B was retained.

Warrant

Engineers shall not review the work of another engineer for the same client except with that engineer's knowledge, unless the other engineer's connection with the work has been terminated; termination removes the notification requirement.

Rebuttal

Would not apply if Engineer A's connection to the work had not actually been terminated, e.g., if he retained an active retainer or ongoing role with the client at the time Engineer B was engaged.

Engineer B Peer Review Notification Duty

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?

Options considered:
O1 Note on each affected sheet exactly what was changed regarding grading, drainage, pipe sizing, sewers, and utilities, so reviewers can distinguish original from revised work. Board's choice
O2 Add a single general statement on the title sheet claiming responsibility for unspecified 'revisions' without detailing individual changes.
O3 Explain the scope of changes to the client directly rather than documenting them on the drawings themselves, treating the plans as unchanged from a documentation standpoint.
Argument structure (Toulmin):
Grounds

Engineer B made changes to grading plans, housing pads, routing of streets, storm drains, pipe dimensions, sewers, and utilities, but placed only a general title-sheet notation about revisions without specifying what those changes were.

Warrant

Engineers must be objective and truthful in professional reports and statements, including all relevant and pertinent information, and must give credit for engineering work to those to whom it is due; a general revision note does not satisfy this duty when substantial specific technical changes were made.

Rebuttal

Would not apply if a general title-sheet revision notation were recognized industry-wide as sufficient shorthand that adequately informs the client and reviewing authorities of the engineer's role, but the Board found the actual notation used here was virtually meaningless without specificity.

Engineer B Change Notation Duty

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?

Options considered:
O1 Add a clear notation acknowledging responsibility for the complete redesigned drawing set, reflecting the fundamental and overall-impact nature of his changes. Board's choice
O2 Place only a general statement about taking responsibility for 'revisions' without specifying scope or full-design impact.
O3 Treat responsibility as limited strictly to the sheets physically altered, on the theory that Engineer A's seal continues to govern the unaltered portions.
Argument structure (Toulmin):
Grounds

Engineer B placed a note on the title sheet stating he was taking responsibility for 'the revisions of the plans' but made no notation of what the changes were, and his changes to grading and public improvement elements were fundamental enough to potentially affect the overall project design.

Warrant

An engineer who makes fundamental changes affecting the overall design of a project must acknowledge responsibility for the full design by notation on the drawings, because responsible charge over a sealed set of plans must be clearly and completely assigned.

Rebuttal

Would not apply if professional convention treats a seal as automatically signifying full responsibility for the sealed document, making an additional explicit full-responsibility notation redundant, though the Board did not find this convention sufficient here.

Engineer B Full Design Responsibility Duty

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?

Options considered:
O1 Formally supersede Engineer A's seal and signature on the sheets containing substantial redesign, sealing those sheets under his own name to eliminate dual claims of responsible charge. Board's choice
O2 Keep Engineer A's seal and signature on all sheets and add only a general note claiming responsibility for unspecified revisions.
O3 Keep Engineer A's seal in place but add a precise, sheet-by-sheet statement delineating exactly which elements Engineer B now takes responsibility for.
Argument structure (Toulmin):
Grounds

Engineer A signed and sealed all sheets of both plan sets; Engineer B made major design changes to the grading and public improvement plans but did not sign any sheets, left Engineer A's seal and signature intact, and added only a general note claiming responsibility for 'revisions'.

Warrant

A professional seal represents a certification of responsible charge over the sealed work; when a second engineer substantially alters sealed plans, responsible charge must be reassigned or clearly bounded so that no document contains two unresolved and inconsistent claims of authorship.

Rebuttal

Would not apply if Engineer B's changes were so clearly and specifically notated as his own responsibility that the intact original seal could be understood by all reviewers as covering only the unaltered original portions, leaving no genuine ambiguity about responsible charge.

Engineer B Revision Responsibility Duty

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?

Options considered:
O1 Mark each sheet or design element clearly to show whether it originated from Engineer A's design or Engineer B's redesign. Board's choice
O2 Add a general note indicating that the plan set contains contributions from both engineers, without specifying which sheets or elements belong to whom.
O3 Sign and seal only the sheets Engineer B created entirely from scratch, leaving modified original sheets under Engineer A's seal without further marking.
Argument structure (Toulmin):
Grounds

Engineer B mixed and matched Engineer A's plans with his own redesign of the grading plan, housing pads, routing of streets, storm drains, pipe dimensions, sewers, and utilities, without marking which portions belonged to which engineer.

Warrant

Engineers must recognize the proprietary interests and give credit for engineering work to those to whom it is due, and must not permit statements that omit material facts; in a mixed-authorship document, third parties relying on the plans need to know whose engineering judgment underlies each portion.

Rebuttal

Would not apply if the vague notation, though general, were still sufficient to alert reviewers that changes had occurred and prompted them to seek clarification before relying on any specific sheet, but the Board found the notation used here rendered this alert virtually meaningless.

Engineer B Work Attribution Duty
Event Timeline (14)
14 sequenced 9 actions 5 events
Case timeline
Engineer A prepared subdivision plans consisting of a 5-sheet grading set and a 38-sheet public improvement set, signing and sealing every sheet including the cover sheets.
Fulfills (1)
  • Acknowledgment of Design Responsibility (Section III.9)
Causal-normative reasoning(confidence 0.75)
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.
The client became dissatisfied with the subdivision plans prepared by Engineer A, which set in motion the discharge and the retention of a successor engineer.
The client, dissatisfied with the plans, discharged Engineer A after paying the complete fee and asked Engineer A for his original drawings.
Causal-normative reasoning(confidence 0.60)
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.
State changes (1)
  • began: Engineer A Post-Discharge Phase
The contractual relationship between Engineer A and the client came to an end as a consequence of the discharge, with the full fee paid, ending Engineer A's status as the retained engineer on the project.
State changes (1)
  • began: Engineer A Post-Discharge Phase
Engineer A complied with the client's request and turned over his original drawings, retaining a set of reproducibles for himself.
Causal-normative reasoning(confidence 0.50)
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.
The client retained Engineer B to review and redesign the project and gave him the set of plans produced by Engineer A to use as a guide in the redesign.
Causal-normative reasoning(confidence 0.60)
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.
Despite the discharge, Engineer A came to maintain an ongoing connection with the project because the client passed his signed and sealed work product along to Engineer B for use in the redesign.
State changes (1)
  • began: Engineer A Post-Discharge Work Connection
Engineer B agreed to review and redesign Engineer A's work for the same client without notifying Engineer A. The Board concedes this acceptance itself was not unethical because the client had discharged Engineer A.
Causal-normative reasoning(confidence 0.65)
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.
State changes (2)
  • began: Engineer B Code Violation Finding
  • began: Engineer B Design Impact Recognition Failure
Engineer B undertook to modify Engineer A's plans without consulting Engineer A, and neither engineer communicated with the other at any point after Engineer B was retained. The Board states it would have been wiser and more professional for Engineer B to consult with Engineer A first.
Causal-normative reasoning(confidence 0.75)
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.
State changes (1)
  • began: No Communications Between Engineers
Engineer B changed the grading plans, deleting one sheet, raising the elevation of the housing pads, and rerouting the street, without noting what changes were made and without signing any of the sheets including the cover sheet.
Violates (2)
  • Duty to Note All Design Changes (Section III.3.a)
  • Acknowledgment of Design Responsibility (Section III.9)
Causal-normative reasoning(confidence 0.85)
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.
State changes (1)
  • began: Undocumented Plan Revisions
Engineer B made major design changes to the storm drains, pipe dimensions, sewers, and utilities in the public improvement plans, with no notation of the changes, without signing the plans, and leaving Engineer A's seal and signature intact.
Violates (2)
  • Duty to Note All Design Changes (Section III.3.a)
  • Acknowledgment of Design Responsibility (Section III.9)
Causal-normative reasoning(confidence 0.85)
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.
State changes (2)
  • began: Undocumented Plan Revisions
  • began: Intact Seal On Revised Plans
Engineer B placed a note on the title sheet of the public improvement plans, leaving Engineer A's signature and seal intact, stating that he was taking responsibility for the revisions of the plans, without noting what those changes were. The Board found this notation virtually meaningless and found that Engineer B failed to acknowledge responsibility for the full design.
Violates (2)
  • Duty to Note All Design Changes (Section III.3.a)
  • Acknowledgment of Design Responsibility (Section III.9)
Causal-normative reasoning(confidence 0.85)
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.
State changes (1)
  • began: Undocumented Plan Revisions
The title sheet notation taking responsibility for revisions became virtually meaningless because Engineer B failed to specify what the changes were.
As a consequence of Engineer B's undocumented modifications while Engineer A's seal and signature remained intact, the plans became misleading, blending the work of both engineers with no indication of which work belonged to whom.
State changes (1)
  • began: Undocumented Plan Revisions
Narrative (3 main characters)
View Extraction
Opening Context

Written in second person from the engineer's point of view, so you read the case as the professional experienced it. Underlined names link to the character's profile below.

You are Engineer B, and you have been retained by a client to review and redesign a subdivision project after the client discharged Engineer A, the original design engineer, upon completion and full payment of the project plans. The client has provided you with Engineer A's complete set of drawings, consisting of a 5-sheet grading plan and a 38-sheet public improvement plan covering storm drains, sewers, pipe dimensions, and utilities, with every sheet in both sets bearing Engineer A's original signature and seal. Your work on the grading plans involves deleting one sheet entirely, raising the elevation of the housing pads, and changing the street routing. Your work on the public improvement plans involves major redesign of the storm drain system, pipe dimensions, sewer layout, and utility placement. Engineer A's seal and signature remain on every sheet, and you have not contacted Engineer A since accepting this assignment. As you prepare to finalize the revised drawings for submission, you must decide how to handle documentation of your changes, whether to add your own notation of responsibility, and what to do about the seals and signatures already on the sheets.

Main characters (3)

Each card shows the roles a person holds and the tensions those roles raise for them. A single person may carry several roles in the case, and a tension between obligations can implicate more than one person at once. Click Show all tensions for the full list.

Engineer B Roles in this case: Reviewing EngineerRedesign Engineer

Guided by: Accountability for Plan Revisions, Responsible Charge over Sealed Plans, Peer Review Without Notification

Engineer B is expected to assume full professional responsibility for the entire redesigned work product when applying a seal, but the constraint requires that Engineer A's original sealed portions remain intact and unaltered. This creates tension between claiming comprehensive responsibility for the design and respecting the boundary of another engineer's independent professional judgment and seal.

Attaches to role: Redesign Engineer

The obligation to notify Engineer A that a peer review of the original design is taking place can conflict in practice with the separate obligation to mark up and note revisions directly on the drawings. Engineer B may prioritize documenting technical changes over the interpersonal duty to inform Engineer A, leaving the original engineer unaware that their sealed work is being reviewed and altered.

Attaches to role: Redesign Engineer

Engineer B's duty to properly credit Engineer A for the original portions of the work can be undermined if revisions are made without clear documentation. Undocumented changes risk creating a false impression about who is responsible for which parts of the design, which conflicts with the attribution duty and can mislead the client and future reviewers.

Attaches to role: Redesign Engineer
Engineer A Roles in this case: Original Design Engineer

Engineer B is expected to assume full professional responsibility for the entire redesigned work product when applying a seal, but the constraint requires that Engineer A's original sealed portions remain intact and unaltered. This creates tension between claiming comprehensive responsibility for the design and respecting the boundary of another engineer's independent professional judgment and seal.

The obligation to notify Engineer A that a peer review of the original design is taking place can conflict in practice with the separate obligation to mark up and note revisions directly on the drawings. Engineer B may prioritize documenting technical changes over the interpersonal duty to inform Engineer A, leaving the original engineer unaware that their sealed work is being reviewed and altered.

Engineer B's duty to properly credit Engineer A for the original portions of the work can be undermined if revisions are made without clear documentation. Undocumented changes risk creating a false impression about who is responsible for which parts of the design, which conflicts with the attribution duty and can mislead the client and future reviewers.

Client Subdivision Roles in this case: Project Client

Engineer B's duty to properly credit Engineer A for the original portions of the work can be undermined if revisions are made without clear documentation. Undocumented changes risk creating a false impression about who is responsible for which parts of the design, which conflicts with the attribution duty and can mislead the client and future reviewers.

The Board’s deliberation

How the Board of Ethical Review resolved the case, verbatim from its published conclusions.

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.
Opening States (7)
Engineer A Post-Discharge Phase Intact Seal On Revised Plans Undocumented Plan Revisions No Communications Between Engineers Engineer B Code Violation Finding Engineer A Post-Discharge Work Connection Engineer B Design Impact Recognition Failure
Summary
  • An engineer who performs a peer review or redesign of another engineer's sealed work is not ethically obligated to notify that original engineer before beginning the work, since the duty runs to the client rather than to the peer.
  • When sealing a redesigned product, Engineer B must clearly delineate which portions were originally sealed by Engineer A and which reflect new work, so responsibility and attribution remain traceable.
  • Documentation of changes on the drawings serves both a technical function and an ethical one, protecting the reputational interests of the original engineer even in the absence of direct communication.

© Licensed under the GNU GPL v3