Step 4: Full View

Entities, provisions, decisions, and narrative

Public Health and Safety— Observed Structural Defects and Inspection by County Building Official
Step 4 of 5

374

Entities

4

Provisions

5

Precedents

17

Questions

24

Conclusions

Transfer

Transformation
Transfer Resolution transfers obligation/responsibility to another party
Engineer A's ethical obligation undergoes a two-stage transfer: first, the duty to inform shifts from Engineer A to Client B upon verbal notification (satisfying the faithful agent obligation); second, and more critically, the duty to protect public safety transfers from Engineer A to supervisory regulatory authorities (the county official's supervisor, fire marshal, or state building authority) upon Engineer A's written escalation — at which point Engineer A has fulfilled the public welfare paramount obligation by enabling the appropriate institutional actors to assume enforcement responsibility. The Board's sequenced framework — notify client first, then escalate in writing to regulatory hierarchy — is structurally a transfer mechanism, not a stalemate, because the Board resolves the client-versus-public tension through hierarchical prioritization rather than leaving competing obligations unresolved.
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 (4)
View Extraction
I.1. Hold paramount the safety, health, and welfare of the public.
How this applies in the case (showing 3 of 129)
Obligation
Engineer A Current Case Non-Imminent Structural Risk Client Collaboration
Holding public safety paramount requires continuing to pursue resolution of the structural safety concern even while collaborating with the client.
Action
Bracing Recommendation to Owners
Recommending bracing directly addresses structural safety to protect public health and welfare.
State
Unlicensed Bridge Inspector Practice - BER Case 00-5
A non-engineer performing structural evaluation of a hazardous bridge directly threatens public safety which engineers must hold paramount.
Obligation (24)
  • Engineer A Current Case Non-Imminent Structural Risk Client Collaboration
    Holding public safety paramount requires continuing to pursue resolution of the structural safety concern even while collaborating with the client.
  • Engineer A BER 00-5 Public Pressure Non-Subordination Bridge Closure
    Holding public safety paramount requires maintaining the bridge closure determination against public pressure.
  • Engineer A BER 00-5 Non-Engineer Override Resistance Full-Bore Escalation
    Holding public safety paramount requires resisting a non-engineer override of a safety-critical bridge closure decision.
  • Engineer A BER 00-5 Five-Ton Limit Strict Enforcement Escalation
    Holding public safety paramount requires pressing for strict enforcement of the weight limit upon observing violations.
  • Engineer A Incidental Structural Observation Disclosure Fire Investigation
    Holding public safety paramount requires disclosing observed structural instability even when retained for a different scope.
  • Engineer A Faithful Agent Immediate Client Notification Structural Hazard
    Holding public safety paramount requires immediately advising the client of observed structural instability.
  • Engineer A Certificate of Occupancy Authority Re-Notification Structural Deficiency
    Holding public safety paramount requires notifying the county building official of a structural deficiency posing a public risk.
  • Engineer A Non-Imminent Collapse Proportionate Response Calibration
    Holding public safety paramount requires a proportionate but real response to a non-imminent structural collapse risk.
  • Engineer A Actionable Bracing Guidance Building Owners
    Holding public safety paramount requires providing specific remedial guidance to prevent collapse.
  • Engineer A Post-Verbal-Notification Written Follow-Up County Official Non-Response
    Holding public safety paramount requires following up in writing when a verbal notification to an official goes unanswered.
  • Engineer A Post-Unresponsive-Official Escalation County Building Official
    Holding public safety paramount requires escalating the structural safety concern when the building official fails to respond.
  • Engineer A Scope-of-Work Non-Shield Structural Disclosure Fire Investigation
    Holding public safety paramount means the contractual scope cannot shield the engineer from disclosing a structural hazard.
  • County Building Official Certificate of Occupancy Authority Non-Response Structural Hazard
    Holding public safety paramount obligates the building official who issued the certificate of occupancy to respond to a reported structural hazard.
  • Engineer A Confidentiality Non-Bar Structural Disclosure County Official
    Holding public safety paramount means client confidentiality cannot bar disclosure of a structural safety hazard to authorities.
  • Engineer A Written Third-Party Safety Notification Building Owners
    Holding public safety paramount requires written notification to building owners of a structural deficiency.
  • Engineer A New Owner Priority Notification Before Official Escalation
    Holding public safety paramount requires notifying the current building owners of the structural deficiency before or alongside official escalation.
  • Engineer A BER 00-5 Imminent Widespread Bridge Collapse Full-Bore Campaign
    Holding public safety paramount requires a full multi-authority escalation campaign when imminent widespread collapse is possible.
  • Engineer A Current Case Certificate of Occupancy Authority Re-Notification
    Holding public safety paramount requires notifying the county building official who issued the certificate of occupancy of the structural deficiency.
  • Engineer A Current Case Post-Unresponsive-County-Official Multi-Agency Escalation
    Holding public safety paramount requires escalating to higher authorities when the county building official fails to respond.
  • Engineer A Current Case Corrective Action Pursuit Scope Calibration
    Holding public safety paramount requires determining how far the obligation to seek corrective action extends.
  • Engineer A BER 07-10 Written Record and Follow-Up Confirmation Obligation
    Holding public safety paramount requires written records and follow-up to ensure structural safety concerns are addressed.
  • Engineer A BER 07-10 Deadline-Conditioned County-State Building Official Escalation
    Holding public safety paramount requires escalating to county or state officials if appropriate steps are not taken within a reasonable period.
  • Engineer A BER 07-10 Proportional Escalation Non-Imminent Barn Collapse
    Holding public safety paramount requires a calibrated escalation response even for non-imminent structural risks.
  • Engineer A Current Case Proportional Escalation Non-Imminent Building Structural Risk
    Holding public safety paramount requires pursuing escalation proportional to the non-imminent but real structural risk.
Action (4)
  • Bracing Recommendation to Owners
    Recommending bracing directly addresses structural safety to protect public health and welfare.
  • Scope Expansion to Structural Assessment
    Expanding scope to assess structural defects is driven by the obligation to protect public safety.
  • Call to County Building Official
    Notifying the building official is an action taken to protect public safety when a structural hazard exists.
  • Decision Not to Further Escalate
    Choosing not to escalate further must be evaluated against the paramount duty to protect public safety.
State (19)
  • Unlicensed Bridge Inspector Practice - BER Case 00-5
    A non-engineer performing structural evaluation of a hazardous bridge directly threatens public safety which engineers must hold paramount.
  • Safety Closure Barrier Removal - BER Case 00-5
    Erecting barricades to close a hazardous bridge is a direct action to protect public safety as required by I.1.
  • Post-Sale Structural Safety Concern - BER Case 07-10
    Structural modifications to a previously engineered barn create a public safety concern that engineers must hold paramount.
  • Certificate of Occupancy Issued Despite Structural Concern - BER Case 07-10
    Issuance of a certificate of occupancy for a structurally compromised barn endangers public safety which engineers must hold paramount.
  • Non-Imminent Structural Collapse Risk - BER Case 07-10
    A barn at risk of collapse under severe snow loads poses a real danger to public safety that engineers must hold paramount.
  • County Building Official Non-Response - Current Case
    The official's failure to respond to a safety notification leaves the public at risk, reinforcing the engineer's obligation to hold public safety paramount.
  • Graduated Escalation Obligation. Non-Imminent Structural Collapse
    The obligation to escalate a non-imminent structural risk stems directly from the duty to hold public safety paramount.
  • Public Safety at Risk. Structural Instability
    Structural instability directly endangers occupants and the public, which is the core concern addressed by I.1.
  • Multi-Authority Escalation Obligation - Bridge Case BER 00-5
    Escalating to multiple authorities after a non-engineer override is driven by the paramount duty to protect public safety.
  • Post-Certificate-of-Occupancy Structural Safety Concern - Current Case
    A structural safety concern in an occupied building directly implicates the duty to hold public safety paramount.
  • Graduated Escalation Calibration - Current Case vs BER 00-5
    Calibrating escalation to the severity of a structural risk is an expression of the duty to hold public safety paramount.
  • Engineer A Forensic Scope-Exceeding Structural Discovery
    Discovering structural instability outside the original scope still triggers the paramount duty to protect public safety.
  • Certificate of Occupancy Issued Despite Structural Deficiency
    An occupied building with a structural deficiency certified by authorities poses a public safety risk engineers must hold paramount.
  • Non-Imminent Structural Collapse Risk
    A building at risk of collapse, even if not imminent, represents a public safety concern engineers must hold paramount.
  • County Building Official Non-Response to Safety Notification
    The official's non-response leaves a structural safety risk unaddressed, reinforcing the engineer's paramount duty to public safety.
  • Post-Certificate-of-Occupancy Structural Safety Concern
    A structural concern in a certified building directly implicates the engineer's duty to hold public safety paramount.
  • Bridge Structural Hazard - BER Case 00-5
    A bridge with rotten pilings 30 feet above a stream is a direct public safety hazard that engineers must hold paramount.
  • Public Pressure Override of Bridge Closure - BER Case 00-5
    Community pressure to reopen a hazardous bridge conflicts with the engineer's duty to hold public safety paramount.
  • Non-Engineer Public Works Director Bridge Reopening Decision - BER Case 00-5
    A non-engineer overriding a bridge closure decision endangers public safety which engineers must hold paramount.
Constraint (19)
  • Engineer A Potential Safety Risk Written Notification Client B
    The paramount safety duty requires Engineer A to notify Client B in writing of the structural instability risk.
  • Engineer A Corrective Action Proportionality Non-Imminent Collapse
    Holding safety paramount requires Engineer A to pursue corrective action calibrated to the real structural collapse risk.
  • Engineer A Verbal-Only Notification Written Follow-Up County Building Official
    The paramount safety duty requires more than a verbal notification when the building official fails to respond.
  • Engineer A Graduated Deadline-Conditioned Escalation County Building Official Non-Response
    Holding safety paramount requires Engineer A to escalate through graduated steps when the county official is unresponsive.
  • Engineer A New Owner Priority Notification Before Official Escalation Current Case Constraint
    The paramount safety duty requires notifying building owners of structural deficiency before or alongside official escalation.
  • Engineer A Scope Limitation Non-Exculpation Structural Safety Fire Case Constraint
    Holding safety paramount means the contracted fire investigation scope cannot excuse Engineer A from disclosing structural instability.
  • Engineer A BER 00-5 Public Pressure Non-Subordination Bridge Closure Constraint
    The paramount safety duty prohibits subordinating a professionally grounded bridge closure determination to public petition pressure.
  • Engineer A BER 00-5 Non-Engineer Override Resistance Full-Bore Escalation Constraint
    Holding safety paramount prohibits acquiescing to a non-engineer override that could compromise structural safety.
  • Engineer A Fire Investigation Scope Non-Shield Structural Disclosure Constraint
    The paramount safety duty means the fire investigation contract scope cannot shield Engineer A from disclosing structural instability.
  • Engineer A Corrective Action Scope Proportionality Current Case Constraint
    Holding safety paramount requires Engineer A to pursue corrective action proportional to the real structural safety risk.
  • Engineer A Persistent Safety Escalation Beyond Unresponsive County Official Constraint
    The paramount safety duty means an unanswered phone call cannot discharge Engineer A's safety reporting obligation.
  • Engineer A BER 00-5 Five-Ton Weight Limit Strict Enforcement Escalation Constraint
    Holding safety paramount requires Engineer A to immediately press for enforcement of the weight limit upon observing violations.
  • Engineer A Forensic Scope Non-Exculpation Structural Disclosure Fire Investigation
    The paramount safety duty means the forensic contract scope cannot excuse Engineer A from disclosing structural instability.
  • Engineer A Certificate of Occupancy Non-Preclusion Safety Duty Fire Investigation
    Holding safety paramount means a prior certificate of occupancy does not discharge Engineer A's duty to report observed structural deficiency.
  • Engineer A Preliminary Structural Assessment Epistemic Qualification Disclosure
    The paramount safety duty requires disclosure of identified structural instability even when the assessment is only preliminary.
  • Engineer A Certificate of Occupancy Non-Preclusion Safety Duty Constraint
    Holding safety paramount means a certificate of occupancy cannot preclude Engineer A's obligation to report structural deficiency.
  • Engineer A Potential Safety Risk Written Notification Constraint
    The paramount safety duty directly requires Engineer A to provide written notification of the structural instability risk to Client B.
  • Engineer A Graduated Deadline-Conditioned Escalation Current Case Constraint
    Holding safety paramount requires Engineer A to follow up verbal notification with written confirmation and escalation steps.
  • Engineer A Verbal-Only Safety Notification Written Follow-Up Current Case Constraint
    The paramount safety duty means a verbal contact that goes unanswered is insufficient as a complete discharge of the safety notification obligation.
Principle (19)
  • Public Welfare Paramount Invoked By Engineer A Fire Investigation
    Engineer A's immediate action to protect the public from a structural hazard directly embodies the paramount duty to protect public safety.
  • Incidental Observation Disclosure Obligation Invoked By Engineer A
    The obligation to disclose an observed structural hazard outside contracted scope is rooted in the duty to hold public welfare paramount.
  • Persistent Escalation Obligation Triggered By County Building Official Non-Response
    The duty to escalate when authorities fail to act stems from the paramount obligation to protect public safety.
  • Third-Party Direct Notification Obligation Invoked By Engineer A To Building Owners
    Directly notifying building owners of collapse risk reflects the duty to protect the safety and welfare of those at risk.
  • Risk Threshold Calibration Invoked By Engineer A Non-Imminent Collapse Assessment
    Calibrating response to a non-imminent but real structural risk reflects the engineer's ongoing duty to protect public welfare proportionally.
  • Confidentiality Non-Applicability Invoked By Engineer A Disclosure To County Official
    Public safety concerns override confidentiality, consistent with the paramount duty to protect public welfare.
  • Scope-of-Work Limitation Non-Defense Invoked By Engineer A Structural Disclosure
    Contractual scope cannot excuse failure to disclose a hazard when public safety is at stake.
  • Post-Client-Refusal Escalation Assessment Obligation Implicated By County Non-Response
    When regulatory authorities fail to act, the engineer's paramount duty to public safety requires further escalation.
  • Public Employee Engineer Heightened Obligation Applied in BER Case 00-5
    A public engineer's heightened duty to act on safety hazards directly reflects the paramount obligation to protect public welfare.
  • Incidental Observation Disclosure Obligation Applied in Current Case
    Disclosing an observed structural hazard outside contracted scope upholds the paramount duty to protect public safety.
  • Risk Threshold Calibration Applied to Current Case
    Assessing and responding to a significant but non-imminent structural risk reflects the duty to protect public welfare.
  • Scope-of-Work Limitation as Incomplete Defense Applied in Current Case
    Contractual scope limitations do not override the paramount duty to disclose safety hazards to the public.
  • Confidentiality Non-Applicability Applied in Current Case
    Public safety disclosure obligations supersede confidentiality, consistent with holding public welfare paramount.
  • Public Welfare Paramount Invoked by Engineer A in Current Case
    This principle entity directly embodies the I.1 provision by describing Engineer A's actions to protect public welfare.
  • Public Welfare Paramount Invoked by Engineer A in BER Case 00-5
    Engineer A's bridge closure decision directly reflects the paramount duty to protect public safety.
  • Proportional Escalation Obligation Invoked in Comparison of BER Cases 00-5 and 07-10
    Proportional escalation based on risk level is a mechanism for fulfilling the paramount duty to protect public safety.
  • Proportional Escalation Obligation Applied to Current Case
    Escalating response to a significant structural risk reflects the duty to hold public welfare paramount.
  • Persistent Escalation Obligation Applied in BER Case 07-10
    Following up in writing when verbal notification is ignored reflects the paramount duty to ensure public safety is addressed.
  • Resistance to Public Pressure Applied in BER Case 00-5
    Maintaining a safety closure against public pressure directly embodies the paramount duty to protect public welfare over other interests.
Role (6)
  • Engineer A Forensic Building Investigation Engineer
    Engineer A observed structural instability and was obligated to hold public safety paramount by reporting the hazard.
  • Engineer A (Current Case) Forensic Building Investigation Engineer
    Engineer A in the current case directly observed structural hazards and had a duty to prioritize public safety above all else.
  • County Building Official Certificate of Occupancy Authority Individual
    The building official issued a certificate of occupancy and failed to respond to safety concerns, implicating the duty to hold public safety paramount.
  • County Building Official (Current Case)
    The county building official failed to return calls about a structural hazard, falling short of the obligation to protect public safety.
  • Engineer A (BER 00-5) Local Government Bridge Safety Engineer
    This engineer ordered bridge closure to protect the public and faced override, directly engaging the paramount duty to public safety.
  • Engineer A (BER 07-10) Post-Sale Safety Notifying Engineer
    This engineer learned of potentially dangerous structural modifications and had a duty to hold public safety paramount by notifying appropriate parties.
Event (3)
  • Fire Occurs at Building
    A fire at the building directly threatens public safety, which engineers are obligated to hold paramount.
  • Structural Instability Discovered
    Discovered structural instability poses an immediate threat to public health and safety that engineers must prioritize.
  • Collapse Risk Remains Unmitigated
    An unmitigated collapse risk is a direct ongoing threat to public safety that engineers are obligated to address.
Resource (8)
  • NSPE_Code_of_Ethics_Building_Investigation
    This resource directly governs Engineer A's obligation to hold public safety paramount, which is the core requirement of I.1.
  • NSPE_Code_of_Ethics_Primary
    This resource is identified as the overriding normative framework establishing the fundamental obligation to protect public health, safety, and welfare, directly embodying I.1.
  • Building_Structural_Safety_Investigation_Standard_FireCase
    This resource governs Engineer A's professional obligations upon discovering structural instability, which flows directly from the I.1. duty to hold public safety paramount.
  • Building_Structural_Safety_Investigation_Standard_Instance
    This resource governs Engineer A's assessment of structural collapse risk, which is directly tied to the I.1. obligation to protect public safety.
  • BER_Case_00-5
    This precedent establishes the full-body obligation to address public safety dilemmas, directly illustrating the application of I.1.
  • BER_Case_89-7
    This precedent establishes that engineers must not bow to pressure when public safety is at stake, directly reinforcing I.1.
  • BER_Case_90-5
    This precedent establishes that engineers must not bow to pressure when public safety is at stake, directly reinforcing I.1.
  • BER_Case_92-6
    This precedent establishes that engineers must not bow to pressure when public safety is at stake, directly reinforcing I.1.
Capability (27)
  • Engineer A Preliminary Structural Instability Assessment Fire Investigation
    Assessing structural instability directly serves the paramount duty to protect public safety.
  • Engineer A Incidental Observation Out-of-Scope Safety Deficiency Identification Fire Investigation
    Identifying a structural safety deficiency during an incidental observation upholds the duty to hold public safety paramount.
  • Engineer A Public Safety Escalation Structural Hazard Fire Investigation
    Escalating a structural collapse risk beyond the client relationship directly reflects the paramount public safety obligation.
  • Engineer A Imminent vs Non-Imminent Risk Threshold Discrimination Fire Investigation
    Correctly calibrating the risk level is necessary to appropriately protect public safety.
  • Engineer A Imminent vs Non-Imminent Risk Escalation Calibration Fire Investigation
    Proportional escalation of a non-imminent risk is a direct expression of the duty to hold public safety paramount.
  • Engineer A Persistent Safety Escalation Beyond Unresponsive Authority Structural Hazard
    Continuing escalation after an unresponsive official reflects the unyielding duty to protect public safety.
  • Engineer A Certificate of Occupancy Authority Re-Notification Structural Deficiency Individual
    Notifying the authority who issued the certificate of occupancy is a direct action to protect public safety.
  • Engineer A Actionable Bracing Guidance Building Owners Individual
    Providing remedial bracing guidance to prevent collapse directly serves the protection of public safety.
  • Engineer A Post-Verbal-Notification Written Follow-Up County Official Non-Response Individual
    Following up in writing after no response ensures the safety concern is not dropped, upholding public safety.
  • Engineer A Post-Unresponsive-Official Multi-Agency Escalation Pathway Navigation Individual
    Navigating escalation to additional agencies when the first authority is unresponsive upholds the paramount public safety duty.
  • Engineer A Written Third-Party Safety Notification Building Owners Individual
    Written notification to building owners about structural deficiency directly protects public safety.
  • Engineer A Confidentiality Non-Bar Structural Disclosure County Official Individual
    Recognizing that confidentiality does not bar disclosure of a structural hazard upholds the paramount public safety obligation.
  • Engineer A BER 00-5 Public Employee Heightened Safety Obligation
    A public employee engineer has a heightened duty to protect public safety, directly reflecting I.1.
  • Engineer A BER 00-5 Five-Ton Limit Strict Enforcement Escalation
    Pressing for strict weight limit enforcement to prevent bridge failure directly protects public safety.
  • Engineer A BER 00-5 Public Pressure Non-Subordination Bridge Closure
    Maintaining a bridge closure against public pressure upholds the paramount duty to protect public safety.
  • Engineer A BER 00-5 Non-Engineer Override Resistance Full-Bore Escalation
    Resisting a non-engineer override of a safety decision directly reflects the paramount public safety obligation.
  • Engineer A BER 00-5 Multi-Precedent Structural Safety Duty Synthesis
    The synthesis of precedents establishes that structural safety issues invoke the fundamental duty to hold public safety paramount.
  • Engineer A Current Case Certificate of Occupancy Authority Re-Notification
    Notifying the certificate-issuing authority of structural deficiency is a direct action to protect public safety.
  • Engineer A Current Case Actionable Bracing Guidance Building Owners
    Providing actionable bracing guidance to prevent collapse directly serves the paramount public safety duty.
  • Engineer A Current Case Scope-of-Work Non-Shield Structural Disclosure
    Recognizing that scope of work does not shield disclosure of a safety hazard upholds the paramount public safety obligation.
  • Engineer A Post-Unresponsive-County-Official Supervisor Fire Marshal Escalation Current Case
    Escalating to additional authorities after an unresponsive official directly serves the paramount duty to protect public safety.
  • Engineer A Imminent vs Non-Imminent Structural Risk Escalation Calibration Current Case
    Calibrating escalation to the nature of the structural risk is necessary to appropriately fulfill the public safety duty.
  • Engineer A BER 07-10 Proportional Escalation Non-Imminent Barn Collapse
    Proportional escalation of a non-imminent structural risk reflects the duty to hold public safety paramount.
  • Engineer A BER 07-10 Written Record and Follow-Up Confirmation
    Maintaining written records of safety communications ensures the public safety concern is properly pursued.
  • Engineer A BER 07-10 Deadline-Conditioned County-State Building Official Escalation
    Escalating to building officials if corrective action is not taken within a reasonable period directly protects public safety.
  • Engineer A Non-Imminent Structural Risk Client Collaboration Current Case
    Collaborating with the client to resolve a structural safety concern alongside escalation serves the public safety duty.
  • Engineer A Corrective Action Pursuit Scope Calibration Current Case
    Determining the extent of the obligation to seek corrective action is directly tied to fulfilling the public safety duty.
I.2. Perform services only in areas of their competence.
How this applies in the case (showing 3 of 21)
Obligation
Engineer A Multi-Credential Structural Competence Activation Fire Investigation
Performing services only in areas of competence requires Engineer A to activate structural engineering credentials when observing structural instability during a fire investigation.
Action
Scope Expansion to Structural Assessment
Expanding into structural assessment requires the engineer to act only within their area of competence.
State
Unlicensed Bridge Inspector Practice - BER Case 00-5
A retired non-engineer performing structural evaluation of a hazardous bridge is acting outside the area of engineering competence required by I.2.
Obligation (4)
  • Engineer A Multi-Credential Structural Competence Activation Fire Investigation
    Performing services only in areas of competence requires Engineer A to activate structural engineering credentials when observing structural instability during a fire investigation.
  • Engineer A Scope-of-Work Non-Shield Structural Disclosure Fire Investigation
    Competence in structural engineering obligates Engineer A to act on observed structural instability regardless of the contracted scope.
  • Engineer A BER 00-5 Retired Inspector Unlicensed Practice Determination Reporting
    Competence obligations require Engineer A to assess whether the retired inspector's activities constituted unlicensed engineering practice.
  • Engineer A BER 00-5 Crutch Pile Adequacy Collaborative Verification
    Performing services within competence requires Engineer A to collaborate with the original inspection firm to verify the adequacy of the crutch piles.
Action (1)
  • Scope Expansion to Structural Assessment
    Expanding into structural assessment requires the engineer to act only within their area of competence.
State (3)
  • Unlicensed Bridge Inspector Practice - BER Case 00-5
    A retired non-engineer performing structural evaluation of a hazardous bridge is acting outside the area of engineering competence required by I.2.
  • Non-Engineer Public Works Director Bridge Reopening Decision - BER Case 00-5
    A non-engineer public works director making a structural safety determination is performing services outside their area of engineering competence.
  • Engineer A Forensic Scope-Exceeding Structural Discovery
    Engineer A discovering structural issues while conducting a fire investigation raises the question of whether structural assessment falls within their retained competence.
Constraint (3)
  • Engineer A Multi-Credential Structural Competence Activation Fire Investigation
    Engineer A's dual credentials in fire investigation and structural engineering mean competence-based awareness of structural instability cannot be disclaimed.
  • Engineer A Multi-Credential Structural Competence Activation Fire Investigation Constraint
    Performing services only within areas of competence means Engineer A's structural engineering credentials activate an obligation to recognize and disclose structural instability.
  • Engineer A BER 00-5 Retired Inspector Unlicensed Practice Determination Reporting Constraint
    The competence provision requires Engineer A to assess whether the retired inspector's activities constitute unlicensed engineering practice.
Principle (2)
  • Multi-Credential Competence Activation Obligation Invoked By Engineer A Structural Expertise
    The obligation to apply structural engineering competence when qualified directly reflects the provision to perform services only within areas of competence.
  • Unlicensed Practice Challenge Obligation Applied in BER Case 00-5
    Determining whether a retired inspector's activities constituted unlicensed practice relates to the requirement that engineers perform only within their areas of competence and licensure.
Role (2)
  • Engineer A Forensic Building Investigation Engineer
    Engineer A was retained for forensic investigation and must perform services only within areas of competence such as fire origin analysis and structural assessment.
  • Engineer A (Current Case) Forensic Building Investigation Engineer
    Engineer A conducted a forensic building investigation and must ensure the structural instability assessment falls within their area of competence.
Resource (2)
  • Structural_Load_Calculation_Standard_FireCase
    This resource provides the technical basis for Engineer A's preliminary structural assessment, which must fall within Engineer A's area of competence as required by I.2.
  • Building_Structural_Safety_Investigation_Standard_FireCase
    This resource governs Engineer A's professional obligations during a structural investigation, which must be performed within the engineer's area of competence per I.2.
Capability (4)
  • Engineer A Preliminary Structural Instability Assessment Fire Investigation
    Performing a structural instability assessment requires that Engineer A act within the area of structural engineering competence.
  • Engineer A Multi-Credential Incidental Observation Competence Activation Fire Investigation
    Recognizing that an incidental observation activates professional obligations depends on Engineer A having the competence to make that structural judgment.
  • Engineer A BER 00-5 Unlicensed Bridge Inspector Practice Determination
    Determining whether the retired inspector's activities constituted unlicensed practice directly relates to the requirement to perform services only within areas of competence.
  • Engineer A BER 00-5 Crutch Pile Adequacy Collaborative Verification
    Collaborating with the firm that prepared the signed and sealed inspection report reflects acting within competence boundaries by verifying adequacy through qualified parties.
II.1.a. If engineers' judgment is overruled under circumstances that endanger life or property, they shall notify their employer or client and such other authority as may be appropriate.
How this applies in the case (showing 3 of 70)
Obligation
Engineer A BER 00-5 Non-Engineer Override Resistance Full-Bore Escalation
When a non-engineer public works director overrides the bridge closure, Engineer A must notify the employer and appropriate authorities as required when judgment is overruled endangering life.
Action
Verbal Notification to Client B
Verbally notifying the client when structural dangers are identified fulfills the duty to notify when judgment is overruled or safety is endangered.
State
Safety Closure Barrier Removal - BER Case 00-5
Removal of Engineer A's safety barriers by others overrules the engineer's safety judgment, triggering the obligation to notify appropriate authorities.
Obligation (9)
  • Engineer A BER 00-5 Non-Engineer Override Resistance Full-Bore Escalation
    When a non-engineer public works director overrides the bridge closure, Engineer A must notify the employer and appropriate authorities as required when judgment is overruled endangering life.
  • Engineer A Post-Unresponsive-Official Escalation County Building Official
    When the county building official fails to respond, Engineer A must escalate to other appropriate authorities as required when a safety concern is not addressed.
  • Engineer A Current Case Post-Unresponsive-County-Official Multi-Agency Escalation
    When the county building official is unresponsive, Engineer A must escalate to supervisors and other authorities as required when circumstances endanger life or property.
  • Engineer A BER 00-5 Imminent Widespread Bridge Collapse Full-Bore Campaign
    When judgment is overruled under circumstances endangering life, Engineer A must notify all appropriate authorities including county, state, and federal bodies.
  • Engineer A BER 07-10 Deadline-Conditioned County-State Building Official Escalation
    If appropriate steps are not taken within a reasonable period, Engineer A must escalate to county or state building officials as other appropriate authorities.
  • Engineer A Post-Verbal-Notification Written Follow-Up County Official Non-Response
    When a verbal notification to an official goes unanswered, Engineer A must follow up in writing and notify other appropriate authorities to ensure the safety concern is addressed.
  • Engineer A Certificate of Occupancy Authority Re-Notification Structural Deficiency
    Engineer A must notify the county building official as an appropriate authority when a structural deficiency endangering life or property is identified.
  • Engineer A Current Case Certificate of Occupancy Authority Re-Notification
    Engineer A must notify the county building official as an appropriate authority upon identifying a structural deficiency following issued occupancy certification.
  • Engineer A BER 00-5 Five-Ton Limit Strict Enforcement Escalation
    Observing violations of the weight limit that endanger life requires Engineer A to press supervisors and notify appropriate authorities for enforcement.
Action (3)
  • Verbal Notification to Client B
    Verbally notifying the client when structural dangers are identified fulfills the duty to notify when judgment is overruled or safety is endangered.
  • Call to County Building Official
    Contacting the county building official is the act of notifying an appropriate authority when life or property is endangered.
  • Decision Not to Further Escalate
    Deciding not to escalate further is directly governed by the requirement to notify appropriate authorities when safety is at risk.
State (11)
  • Safety Closure Barrier Removal - BER Case 00-5
    Removal of Engineer A's safety barriers by others overrules the engineer's safety judgment, triggering the obligation to notify appropriate authorities.
  • County Building Official Non-Response - Current Case
    The official's failure to respond after notification requires Engineer A to escalate to other appropriate authorities as specified by II.1.a.
  • Graduated Escalation Obligation. Non-Imminent Structural Collapse
    The obligation to escalate to additional authorities when the county official is unresponsive directly reflects the requirement of II.1.a.
  • Multi-Authority Escalation Obligation - Bridge Case BER 00-5
    After a non-engineer overrides the bridge closure, Engineer A must notify the employer and other appropriate authorities per II.1.a.
  • Post-Certificate-of-Occupancy Structural Safety Concern - Current Case
    When the county official is unresponsive to a safety concern, Engineer A must notify other appropriate authorities as required by II.1.a.
  • Graduated Escalation Calibration - Current Case vs BER 00-5
    Calibrating escalation to intermediate severity while still notifying appropriate authorities reflects the graduated application of II.1.a.
  • Verbal-Only Safety Advisory Without Written Record - BER Case 07-10
    A verbal-only notification without written record may be insufficient to satisfy the notification obligation to appropriate authorities under II.1.a.
  • County Building Official Non-Response to Safety Notification
    The official's non-response to Engineer A's notification requires escalation to other appropriate authorities as mandated by II.1.a.
  • Post-Certificate-of-Occupancy Structural Safety Concern
    An unaddressed structural concern after official notification requires Engineer A to escalate to other authorities per II.1.a.
  • Public Pressure Override of Bridge Closure - BER Case 00-5
    Community pressure leading to a bridge reopening overrules the engineer's safety judgment, triggering the notification obligation of II.1.a.
  • Non-Engineer Public Works Director Bridge Reopening Decision - BER Case 00-5
    A non-engineer overriding the bridge closure overrules the engineer's judgment, requiring notification to the employer and appropriate authorities per II.1.a.
Constraint (9)
  • Engineer A Verbal-Only Notification Written Follow-Up County Building Official
    This provision requires Engineer A to notify appropriate authorities beyond just the client when safety is endangered, making a verbal-only contact insufficient.
  • Engineer A Graduated Deadline-Conditioned Escalation County Building Official Non-Response
    This provision requires Engineer A to notify appropriate authorities when safety is endangered, mandating escalation when the county official is unresponsive.
  • Engineer A BER 00-5 Public Pressure Non-Subordination Bridge Closure Constraint
    This provision requires Engineer A to notify appropriate authorities when judgment is overruled, prohibiting subordination to public petition pressure.
  • Engineer A BER 00-5 Non-Engineer Override Resistance Full-Bore Escalation Constraint
    This provision requires Engineer A to notify appropriate authorities when a non-engineer overrides a safety determination that endangers life or property.
  • Engineer A Persistent Safety Escalation Beyond Unresponsive County Official Constraint
    This provision requires notification to appropriate authorities when safety is endangered, meaning an unanswered call cannot discharge the reporting obligation.
  • Engineer A BER 00-5 Five-Ton Weight Limit Strict Enforcement Escalation Constraint
    This provision requires Engineer A to notify appropriate authorities when circumstances endanger life, including pressing supervisors for weight limit enforcement.
  • Engineer A Graduated Deadline-Conditioned Escalation Current Case Constraint
    This provision requires Engineer A to notify appropriate authorities when safety is endangered, mandating written follow-up and escalation beyond an unresponsive official.
  • Engineer A Verbal-Only Safety Notification Written Follow-Up Current Case Constraint
    This provision requires notification to appropriate authorities when life or property is endangered, making a verbal-only unanswered contact insufficient.
  • Engineer A New Owner Priority Notification Before Official Escalation Current Case Constraint
    This provision requires Engineer A to notify appropriate authorities including building owners when structural deficiency endangers life or property.
Principle (12)
  • Persistent Escalation Obligation Triggered By County Building Official Non-Response
    When the county official failed to respond, Engineer A's obligation to notify other appropriate authorities mirrors the escalation duty in II.1.a.
  • Written Documentation Requirement Implicated By Engineer A Phone Call
    Supplementing verbal notifications with written documentation supports the formal notification obligation to employers, clients, and appropriate authorities.
  • Third-Party Direct Notification Obligation Invoked By Engineer A To Building Owners
    Notifying building owners of structural risk reflects the duty to notify appropriate parties when safety is endangered.
  • Faithful Agent Notification Obligation Invoked By Engineer A To Client B
    Immediately advising Client B of the structural hazard reflects the duty to notify the employer or client when safety is at risk.
  • Post-Client-Refusal Escalation Assessment Obligation Implicated By County Non-Response
    When the regulatory authority fails to act, the engineer must notify other appropriate authorities, consistent with II.1.a escalation requirements.
  • Public Employee Engineer Heightened Obligation Applied in BER Case 00-5
    Engineer A's compulsion to act as both professional engineer and public employee when safety is at risk reflects the notification and escalation duty of II.1.a.
  • Proportional Escalation Obligation Invoked in Comparison of BER Cases 00-5 and 07-10
    The distinction between full-bore and moderate escalation based on risk level reflects the II.1.a duty to notify appropriate authorities calibrated to circumstances.
  • Proportional Escalation Obligation Applied to Current Case
    Escalating to appropriate authorities for a significant but non-imminent risk reflects the II.1.a notification obligation.
  • Persistent Escalation Obligation Applied in BER Case 07-10
    Following up in writing after verbal notification was ignored reflects the II.1.a duty to notify appropriate authorities when safety concerns are not addressed.
  • Written Documentation Requirement Applied in BER Case 07-10
    The requirement to make written records of safety communications directly supports the formal notification duty in II.1.a.
  • Third-Party Direct Notification Obligation Applied in BER Case 07-10
    Notifying the property owner of structural concerns reflects the II.1.a duty to notify appropriate parties when life or property is endangered.
  • Resistance to Public Pressure Applied in BER Case 00-5
    Maintaining the bridge closure and notifying appropriate authorities despite public pressure reflects the II.1.a duty to escalate safety concerns regardless of opposition.
Role (4)
  • Engineer A Forensic Building Investigation Engineer
    Engineer A notified the client and county building official of the structural hazard after observing conditions that could endanger life or property.
  • Engineer A (Current Case) Forensic Building Investigation Engineer
    Engineer A reported the structural instability to Client B and attempted to notify the county building official as an appropriate authority.
  • Engineer A (BER 00-5) Local Government Bridge Safety Engineer
    This engineer faced a supervisor override on a safety decision and was obligated to notify appropriate authorities when judgment was overruled under dangerous circumstances.
  • Engineer A (BER 07-10) Post-Sale Safety Notifying Engineer
    This engineer learned of unsafe modifications post-sale and had an obligation to notify appropriate authorities about conditions endangering life or property.
Event (2)
  • County Official Call Unanswered
    When the county official is unreachable, engineers must escalate notification to other appropriate authorities to address the endangerment.
  • Collapse Risk Remains Unmitigated
    An unresolved collapse risk that endangers life requires engineers to notify appropriate authorities when normal channels fail.
Resource (5)
  • Engineer_Public_Safety_Escalation_Standard_FireCase
    This resource directly governs Engineer A's duty to escalate the structural safety concern to the county building official when the client fails to act, which is the core requirement of II.1.a.
  • Engineer_Public_Safety_Escalation_Standard_Instance
    This resource is the operative professional norm governing how far an engineer's obligation to seek corrective action reaches when a client or authority fails to act, directly applying II.1.a.
  • Engineer_Safety_Recommendation_Rejection_Standard_FireCase
    This resource governs Engineer A's obligations after a safety recommendation is rejected, including determining whether to notify other authorities, which is precisely what II.1.a. requires.
  • BER_Case_07-10
    This precedent establishes the proportionality principle in public safety escalation obligations, directly informing the application of II.1.a. when danger is significant but not imminent.
  • BER_Case_00-5
    This precedent illustrates how the Board addresses public safety dilemmas and the obligation to notify appropriate authorities, directly supporting II.1.a.
Capability (15)
  • Engineer A Faithful Agent Immediate Client Notification Structural Hazard Individual
    Notifying the client upon discovering a structural hazard directly fulfills the obligation to notify the employer or client when safety is endangered.
  • Engineer A Certificate of Occupancy Authority Re-Notification Structural Deficiency Individual
    Notifying the county building official as an appropriate authority when a structural deficiency is identified directly reflects II.1.a.
  • Engineer A Post-Verbal-Notification Written Follow-Up County Official Non-Response Individual
    Following up in writing after the official did not respond ensures the required notification to appropriate authority is completed.
  • Engineer A Post-Unresponsive-Official Multi-Agency Escalation Pathway Navigation Individual
    Escalating to additional authorities when the first is unresponsive fulfills the obligation to notify such other authority as may be appropriate.
  • Engineer A Written Third-Party Safety Notification Building Owners Individual
    Written notification to building owners about the structural deficiency constitutes notification to an appropriate authority as required by II.1.a.
  • Engineer A Confidentiality Non-Bar Structural Disclosure County Official Individual
    Recognizing that confidentiality does not bar disclosure to the county official enables the required notification under II.1.a.
  • Engineer A BER 00-5 Non-Engineer Override Resistance Full-Bore Escalation
    Resisting the non-engineer override and escalating fully reflects the duty to notify appropriate authority when judgment is overruled in circumstances endangering life.
  • Engineer A BER 00-5 Five-Ton Limit Strict Enforcement Escalation
    Pressing the supervisor for strict enforcement after observing dangerous overloading constitutes notifying the employer of circumstances endangering life or property.
  • Engineer A BER 00-5 Public Pressure Non-Subordination Bridge Closure
    Maintaining the bridge closure and explaining the safety rationale to the supervisor reflects notifying the employer when circumstances endanger life.
  • Engineer A Current Case Certificate of Occupancy Authority Re-Notification
    Notifying the certificate-issuing county official of the structural deficiency directly fulfills the II.1.a. notification obligation.
  • Engineer A Post-Unresponsive-County-Official Supervisor Fire Marshal Escalation Current Case
    Escalating to the supervisor and fire marshal after the county official is unresponsive fulfills the obligation to notify such other authority as may be appropriate.
  • Engineer A BER 07-10 New Owner Priority Notification Before Town Supervisor
    Notifying the current owner and town supervisor of the structural deficiency fulfills the obligation to notify the client and appropriate authority.
  • Engineer A BER 07-10 Written Record and Follow-Up Confirmation
    Making written records and following up verbal communications ensures the required notifications under II.1.a. are documented and completed.
  • Engineer A BER 07-10 Deadline-Conditioned County-State Building Official Escalation
    Escalating to county or state building officials if corrective action is not taken fulfills the obligation to notify appropriate authority under II.1.a.
  • Engineer A Persistent Safety Escalation Beyond Unresponsive Authority Structural Hazard
    Continuing to notify additional authorities after an unresponsive official fulfills the II.1.a. obligation to notify such other authority as may be appropriate.
III.1.b. Engineers shall advise their clients or employers when they believe a project will not be successful.
How this applies in the case (showing 3 of 44)
Obligation
Engineer A Faithful Agent Immediate Client Notification Structural Hazard
As faithful agent, Engineer A must advise the client of the observed structural instability indicating the project or structure will not be safe or successful.
Action
Verbal Notification to Client B
Advising Client B of the structural concerns fulfills the duty to inform clients when a project or condition will not be successful or safe.
State
Post-Sale Structural Safety Concern - BER Case 07-10
Engineer A should advise the relevant parties that the structural modifications to the barn compromise its integrity and the project outcome will not be safe.
Obligation (6)
  • Engineer A Faithful Agent Immediate Client Notification Structural Hazard
    As faithful agent, Engineer A must advise the client of the observed structural instability indicating the project or structure will not be safe or successful.
  • Engineer A Current Case Non-Imminent Structural Risk Client Collaboration
    Engineer A must advise Client B of the structural safety concern, as the building in its current state will not be safe without corrective action.
  • Engineer A Actionable Bracing Guidance Building Owners
    Engineer A must advise building owners with specific remedial guidance, informing them that without corrective action the structure will not be safe.
  • Engineer A BER 07-10 New Owner Priority Notification Before Town Supervisor
    Engineer A must first advise the current owner of the structural deficiency, informing them the structure will not be safe without intervention.
  • Engineer A Written Third-Party Safety Notification Building Owners
    Engineer A must advise building owners in writing of the structural deficiency indicating the building will not remain safe without corrective action.
  • Engineer A New Owner Priority Notification Before Official Escalation
    Engineer A must notify the current building owners of the structural deficiency before escalating, fulfilling the duty to advise clients of project safety concerns.
Action (2)
  • Verbal Notification to Client B
    Advising Client B of the structural concerns fulfills the duty to inform clients when a project or condition will not be successful or safe.
  • Bracing Recommendation to Owners
    Recommending bracing to owners constitutes advising the client of necessary corrective action when the structure is at risk.
State (8)
  • Post-Sale Structural Safety Concern - BER Case 07-10
    Engineer A should advise the relevant parties that the structural modifications to the barn compromise its integrity and the project outcome will not be safe.
  • Certificate of Occupancy Issued Despite Structural Concern - BER Case 07-10
    Engineer A should advise the client or employer that the barn extension with compromised structural integrity will not result in a safe and successful project.
  • Verbal-Only Safety Advisory Without Written Record - BER Case 07-10
    A verbal-only advisory without written record may be insufficient to fulfill the obligation to formally advise clients or employers of project failure risk under III.1.b.
  • Engineer A Fire Investigation Engagement
    Upon discovering structural instability during the fire investigation, Engineer A should advise Client B that the building's structural condition poses a risk to a successful outcome.
  • Engineer A Forensic Scope-Exceeding Structural Discovery
    Discovering structural instability outside the original scope obligates Engineer A to advise the client that the building will not be safe or successful in its current state.
  • Certificate of Occupancy Issued Despite Structural Deficiency
    Engineer A should advise the client that the building with a structural deficiency will not be successful or safe despite the certificate of occupancy.
  • Client Relationship - Engineer A and Client B
    The professional relationship between Engineer A and Client B is the direct context in which Engineer A must advise the client of the structural safety concern per III.1.b.
  • Non-Imminent Structural Collapse Risk
    Engineer A should advise the client that the building at risk of collapse under certain conditions will not be a successful or safe project without remediation.
Constraint (8)
  • Engineer A Potential Safety Risk Written Notification Client B
    This provision requires Engineer A to advise Client B in writing that the structural instability means the building may not be safe or successful in its current condition.
  • Engineer A Scope Limitation Non-Exculpation Structural Safety Fire Case Constraint
    This provision requires Engineer A to advise the client of the structural deficiency regardless of the contracted fire investigation scope.
  • Engineer A Fire Investigation Scope Non-Shield Structural Disclosure Constraint
    This provision requires Engineer A to advise the client of the structural instability even though the contract scope was limited to fire investigation.
  • Engineer A Forensic Scope Non-Exculpation Structural Disclosure Fire Investigation
    This provision requires Engineer A to advise the client that the project outcome is at risk due to structural instability, regardless of the forensic contract scope.
  • Engineer A Preliminary Structural Assessment Epistemic Qualification Disclosure
    This provision requires Engineer A to advise Client B of the identified structural instability and its implications even when findings are preliminary.
  • Engineer A Potential Safety Risk Written Notification Constraint
    This provision directly requires Engineer A to advise Client B in writing of the structural instability risk that could affect the project outcome.
  • Engineer A Certificate of Occupancy Non-Preclusion Safety Duty Fire Investigation
    This provision requires Engineer A to advise the client of the structural deficiency even though a certificate of occupancy was previously issued.
  • Engineer A Certificate of Occupancy Non-Preclusion Safety Duty Constraint
    This provision requires Engineer A to advise the client that the structural deficiency is a real concern despite the prior certificate of occupancy.
Principle (4)
  • Faithful Agent Notification Obligation Invoked By Engineer A To Client B
    Advising Client B of the structural instability and preliminary findings reflects the duty to inform clients when a project situation poses risks to success or safety.
  • Written Documentation Requirement Implicated By Engineer A Phone Call
    Documenting communications with the client about the structural hazard supports the obligation to formally advise clients of significant concerns.
  • Written Documentation Requirement Applied in BER Case 07-10
    Making a written record of concerns communicated to the owner reflects the duty to formally advise clients when a project will not be successful or poses risks.
  • Third-Party Direct Notification Obligation Applied in BER Case 07-10
    Notifying the property owner of structural concerns before escalating to authorities reflects the duty to advise clients of project risks first.
Role (3)
  • Engineer A Forensic Building Investigation Engineer
    Engineer A advised Client B of the structural instability, fulfilling the duty to inform clients when a project or structure will not be successful or safe.
  • Engineer A (Current Case) Forensic Building Investigation Engineer
    Engineer A notified Client B of the observed structural hazards, consistent with the obligation to advise clients when conditions indicate failure or danger.
  • Engineer A (BER 07-10) Post-Sale Safety Notifying Engineer
    This engineer believed the structural modifications would create a collapse risk and had a duty to advise relevant parties that the project would not be successful or safe.
Event (2)
  • Structural Instability Discovered
    Upon discovering structural instability, engineers are obligated to advise clients or employers that the project or building cannot safely proceed.
  • Certificate of Occupancy Invalidated
    Invalidation of the certificate of occupancy signals project failure that engineers must communicate to their clients or employers.
Resource (4)
  • Engineer_Safety_Recommendation_Rejection_Standard_FireCase
    This resource governs Engineer A's obligations after recommending bracing and having that recommendation rejected, which directly implicates the III.1.b. duty to advise clients when a project will not be successful.
  • NSPE_Code_of_Ethics_Building_Investigation
    This resource governs Engineer A's obligation to advise the client of risks associated with the structural danger, directly connecting to III.1.b.
  • Certificate_of_Occupancy_Regulatory_Framework_FireCase
    This resource provides context for understanding the client's situation regarding the certificate of occupancy, against which Engineer A must advise the client of risks per III.1.b.
  • Certificate_of_Occupancy_Regulatory_Framework_Instance
    This resource is the regulatory backdrop against which Engineer A's post-issuance safety concern obligations are evaluated, informing the III.1.b. duty to advise the client.
Capability (7)
  • Engineer A Faithful Agent Immediate Client Notification Structural Hazard Individual
    Notifying the client of the structural hazard advises the client of a condition that threatens the success and safety of the project.
  • Engineer A Actionable Bracing Guidance Building Owners Individual
    Providing actionable remedial guidance to the building owners advises the client on steps needed to address a condition threatening project success.
  • Engineer A Scope-of-Work Non-Shield Structural Disclosure Fire Investigation Individual
    Recognizing that the scope of work does not shield disclosure reflects the duty to advise the client of conditions threatening project success regardless of contract scope.
  • Engineer A Current Case Actionable Bracing Guidance Building Owners
    Providing bracing guidance to building owners advises the client of necessary corrective action to prevent project failure.
  • Engineer A Current Case Scope-of-Work Non-Shield Structural Disclosure
    Disclosing the structural deficiency despite the contracted scope reflects the obligation to advise the client when a project will not be successful.
  • Engineer A Non-Imminent Structural Risk Client Collaboration Current Case
    Collaborating with the client to resolve the structural concern reflects the duty to advise and work with the client when a project faces a significant problem.
  • Engineer A Corrective Action Pursuit Scope Calibration Current Case
    Determining the extent of the obligation to seek corrective action with the client reflects the duty to advise the client when a project will not be successful.
Cross-Case Connections
View Extraction
Explicit Board-Cited Precedents 5 Lineage Graph

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

Principle Established:

When an engineer identifies a significant public safety danger, the engineer must take immediate and persistent steps to contact all relevant authorities, including supervisors, state/federal officials, licensure boards, and county commissioners, to ensure the danger is addressed, and failure to do so is an abrogation of fundamental professional responsibility.

Citation Context:

The Board cited this case as a primary illustration of how engineers must respond to public safety threats, establishing the standard for aggressive action when public danger is present. It is also used as a comparator case to distinguish the level of response required in different situations.

Relevant Excerpts
discussion: "An illustration of how the Board has addressed this dilemma can be found in BER Case No. 00-5 . In this case, Engineer A worked for a local government and learned about a critical situation involving a bridge"
discussion: "In determining Engineer A's ethical obligation under these circumstances, the Board decided that Engineer A should have taken immediate steps to press his supervisor for strict enforcement of the five-ton limit"
discussion: "In reaching its conclusion, the Board distinguished BER Case 00-5 from BER Case 07-10 , noting that the facts and circumstances of BER Case 07-10 were different in several respects from those in BER Case 00-5"

Principle Established:

Issues of public health and safety are at the core of engineering ethics, and an engineer who yields to public pressure or employment situations when great dangers are present abrogates their most fundamental professional responsibility.

Citation Context:

The Board cited this case, along with 90-5 and 92-6, to reinforce the principle that public health and safety issues are at the core of engineering ethics and that engineers cannot bow to public pressure or employment pressures when great dangers are present.

Relevant Excerpts
discussion: "Reviewing earlier Board of Ethical Review Case Nos. 89-7 , 90-5 , and 92-6 , the Board noted that the facts and circumstances facing Engineer A "involved basic and fundamental issues of public health and safety"

Principle Established:

When a structural danger exists but is not imminent or widespread, an engineer fulfills ethical obligations by notifying the relevant authority and the owner in writing, following up if no action is taken, and escalating to higher authorities if the situation remains unresolved within a reasonable time.

Citation Context:

The Board cited this case as the closest analogy to the current case, involving a structural danger that was not imminent, where the engineer's obligation was to notify the appropriate authority in writing and follow up, rather than mount a 'full-bore' campaign. It is also distinguished from BER Case 00-5 to calibrate the appropriate level of response.

Relevant Excerpts
discussion: "In BER Case 07-10 , the Board was faced with a case in which Engineer A had designed and built a barn with horse stalls on his property."
discussion: "In reaching its conclusion, the Board distinguished BER Case 00-5 from BER Case 07-10 , noting that the facts and circumstances of BER Case 07-10 were different in several respects from those in BER Case 00-5"
discussion: "The BER concluded that in BER Case 07-10 , the limited nature of the danger did not appear to require this (higher) level of response."

Principle Established:

Issues of public health and safety are at the core of engineering ethics, and an engineer who yields to public pressure or employment situations when great dangers are present abrogates their most fundamental professional responsibility.

Citation Context:

The Board cited this case, along with 89-7 and 90-5, to reinforce the principle that public health and safety issues are at the core of engineering ethics and that engineers cannot bow to public pressure or employment pressures when great dangers are present.

Relevant Excerpts
discussion: "Reviewing earlier Board of Ethical Review Case Nos. 89-7 , 90-5 , and 92-6 , the Board noted that the facts and circumstances facing Engineer A "involved basic and fundamental issues of public health and safety"

Principle Established:

Issues of public health and safety are at the core of engineering ethics, and an engineer who yields to public pressure or employment situations when great dangers are present abrogates their most fundamental professional responsibility.

Citation Context:

The Board cited this case, along with 89-7 and 92-6, to reinforce the principle that public health and safety issues are at the core of engineering ethics and that engineers cannot bow to public pressure or employment pressures when great dangers are present.

Relevant Excerpts
discussion: "Reviewing earlier Board of Ethical Review Case Nos. 89-7 , 90-5 , and 92-6 , the Board noted that the facts and circumstances facing Engineer A "involved basic and fundamental issues of public health and safety"
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 69% Facts Similarity 69% Discussion Similarity 94% Provision Overlap 100% Outcome Alignment 50% Tag Overlap 83%
Shared provisions: I.1, II.1, II.1.a, III.1.b, III.2, III.2.b View Synthesis
Component Similarity 47% Facts Similarity 49% Discussion Similarity 63% Provision Overlap 83% Outcome Alignment 100% Tag Overlap 67%
Shared provisions: I.1, II.1, II.1.a, III.1.b, III.2 Same outcome True View Synthesis
Component Similarity 65% Facts Similarity 68% Discussion Similarity 91% Provision Overlap 57% Outcome Alignment 100% Tag Overlap 43%
Shared provisions: I.1, II.1, II.1.a, III.2 Same outcome True View Synthesis
Component Similarity 55% Facts Similarity 51% Discussion Similarity 69% Provision Overlap 67% Outcome Alignment 100% Tag Overlap 43%
Shared provisions: I.1, II.1, II.1.a, III.1.b Same outcome True View Synthesis
Component Similarity 59% Facts Similarity 73% Discussion Similarity 56% Provision Overlap 57% Outcome Alignment 100% Tag Overlap 43%
Shared provisions: I.1, II.1, II.1.a, III.1.b Same outcome True View Synthesis
Component Similarity 46% Facts Similarity 48% Discussion Similarity 64% Provision Overlap 62% Outcome Alignment 100% Tag Overlap 38%
Shared provisions: I.1, II.1, II.1.a, III.1.b, III.2 Same outcome True View Synthesis
Component Similarity 63% Facts Similarity 55% Discussion Similarity 71% Provision Overlap 83% Tag Overlap 57%
Shared provisions: I.1, II.1, II.1.a, III.1.b, III.2 View Synthesis
Component Similarity 62% Facts Similarity 76% Discussion Similarity 41% Provision Overlap 33% Outcome Alignment 100% Tag Overlap 38%
Shared provisions: I.1, II.1, II.1.a Same outcome True View Synthesis
Component Similarity 53% Facts Similarity 52% Discussion Similarity 65% Provision Overlap 44% Outcome Alignment 100% Tag Overlap 44%
Shared provisions: I.1, II.1, II.1.a, III.1.b Same outcome True View Synthesis
Component Similarity 53% Facts Similarity 47% Discussion Similarity 69% Provision Overlap 46% Outcome Alignment 100% Tag Overlap 33%
Shared provisions: I.1, II.1, II.1.a, III.1.b, III.2 Same outcome True View Synthesis
Questions & Conclusions (1 board)
View Extraction
Board Board question 1

What are Engineer A’s ethical obligations under the circumstances?

Board conclusion Engineer A had an obligation to continue to pursue a resolution of the matter by working with Client B and in contacting in writing the supervisor of the county official, the fire marshal, or any other agency with jurisdiction, advising them of the structural deficiencies.
I.1. II.1.a. III.1.b.
Implicit (4)

Does Engineer A's obligation to escalate beyond the unresponsive county building official change if Client B objects to further disclosure, and at what point does Engineer A's duty to the public override the faithful agent duty to the client?

AnalyticalIn response to Q101: Engineer A's obligation to escalate beyond the unresponsive county building official does not diminish simply because Client B objects to further disclosure. The faithful agent duty owed to Client B is a real and important professional obligation, but it is explicitly subordinate to the paramount duty to protect public safety under NSPE Code Section I.1. Once Engineer A has notified Client B of the structural deficiency - satisfying the faithful agent notification obligation - and the county building official has failed to respond, the public welfare paramount principle takes over as the controlling ethical norm. Client B's preference to avoid costly remediation or regulatory scrutiny cannot serve as a veto over Engineer A's independent duty to the public. The threshold at which public welfare overrides the faithful agent duty is crossed when: (1) a credible structural hazard has been identified, (2) the client has been informed, and (3) the designated regulatory authority has failed to act. All three conditions are satisfied here. At that point, Engineer A's obligation to escalate in writing to the county official's supervisor, the fire marshal, or other agencies with jurisdiction is not merely permissible - it is ethically required, regardless of Client B's preferences.

Because Engineer A's structural assessment was described as 'preliminary,' does the epistemic uncertainty of that assessment affect the threshold at which escalation becomes obligatory, and should Engineer A have sought a more definitive structural evaluation before contacting regulatory authorities?

AnalyticalIn response to Q102: The preliminary nature of Engineer A's structural assessment does affect the manner in which escalation should be framed, but it does not raise the threshold at which escalation becomes obligatory. Engineer A's professional judgment - even when preliminary - that the building is at risk of collapse due to insufficient lateral restraint is sufficient to trigger the disclosure and escalation obligations under the NSPE Code. A preliminary assessment by a licensed structural engineer is not equivalent to uninformed speculation; it reflects professional competence applied to observed conditions. However, the epistemic qualification of 'preliminary' does impose a corresponding obligation of epistemic honesty: Engineer A should communicate the preliminary nature of the assessment clearly in any written escalation, recommend that a more definitive structural evaluation be conducted, and avoid overstating certainty. The preliminary characterization thus shapes the content and tone of the escalation rather than its necessity. Waiting for a definitive evaluation before notifying authorities would be ethically impermissible if the building remained occupied during that interval, because the risk - though non-imminent - is real and the certificate of occupancy creates a false assurance of safety.

Does the fact that a county building official already issued a certificate of occupancy following the structural modifications create a heightened or diminished obligation for Engineer A to escalate, given that the official's prior action implicitly endorsed the building's safety?

AnalyticalIn response to Q103: The county building official's prior issuance of a certificate of occupancy following the structural modifications does not diminish Engineer A's escalation obligation - it heightens it. The certificate of occupancy creates a legally and socially authoritative signal to occupants and the public that the building is safe. When Engineer A's professional assessment contradicts that signal, the gap between official assurance and actual structural condition represents a compounded public safety risk: occupants are not merely unwarned, they are affirmatively misled by the certificate. This makes the county building official's non-response to Engineer A's phone call particularly consequential, because the official's silence perpetuates a false safety assurance. Far from suggesting that the matter has already been reviewed and resolved, the certificate of occupancy issued after the very modifications that Engineer A identifies as the source of structural deficiency raises a serious question about whether the official's prior inspection was adequate. Engineer A's escalation obligation is therefore not weakened by deference to the official's prior judgment; rather, the official's apparent failure to detect the deficiency is itself a reason to escalate to supervisory and alternative regulatory authorities.

What are Engineer A's ongoing obligations if the building owners decline to implement the recommended bracing, and does that refusal independently trigger a duty to escalate to additional authorities even absent the county official's non-response?

AnalyticalIn response to Q104: The building owners' refusal to implement the recommended bracing independently triggers an escalation obligation, separate from and in addition to the obligation triggered by the county building official's non-response. When Engineer A recommends a specific corrective action - bracing - to prevent a known structural collapse risk, and the owners decline to act, the structural hazard remains unmitigated. At that point, Engineer A has exhausted the remedies available through direct advisory action to the parties most immediately responsible for the building. The combination of owner inaction and official non-response leaves the public exposed to a risk that Engineer A has identified and that no responsible party has addressed. Under NSPE Code Section I.1 and the persistent escalation obligation, Engineer A's duty to hold public welfare paramount requires escalation to supervisory authorities, the fire marshal, or other agencies with jurisdiction. The owners' refusal is not merely a private business decision; it is a decision that affects the safety of anyone who enters or occupies the building, and Engineer A cannot ethically treat it as the end of the matter.
Cross-cutting analytical questions (12)

These questions consider the case as a whole rather than a specific board question above.

Principle tension (4)

Does the Faithful Agent Notification Obligation to Client B conflict with the Public Welfare Paramount principle when Client B, having been notified, might prefer that Engineer A not escalate further to supervisory or alternative regulatory authorities who could impose costly remediation or liability?

AnalyticalIn response to Q201: The tension between the faithful agent notification obligation to Client B and the public welfare paramount principle is real but resolvable through sequencing rather than subordination. Engineer A satisfies the faithful agent obligation by notifying Client B first and promptly - which the facts confirm was done. Once that notification is complete, the faithful agent obligation does not extend to suppressing or deferring further escalation at Client B's request when public safety is at stake. The NSPE Code's structure is hierarchical: Section I.1 places public welfare paramount, and the faithful agent duty in Section III is explicitly bounded by that hierarchy. Client B's potential preference to avoid regulatory scrutiny or remediation costs is a legitimate business interest, but it is not an interest that Engineer A is ethically permitted to protect at the expense of public safety. The resolution of the tension is therefore: notify Client B first, document that notification, and then proceed with escalation to regulatory authorities regardless of Client B's preferences, because the faithful agent duty does not include the duty to suppress safety-critical information from public authorities.
AnalyticalThe tension between the Faithful Agent Notification Obligation and the Public Welfare Paramount principle was resolved in this case through a sequenced, not competing, framework: Engineer A's duty to Client B was satisfied first by immediate verbal notification of the structural deficiency, but that satisfaction did not exhaust Engineer A's obligations. Once Client B was informed and the county building official failed to respond, the Public Welfare Paramount principle assumed unambiguous priority. The case teaches that faithful agency and public welfare are not symmetrically weighted duties - client loyalty operates within a ceiling defined by public safety, and when a non-imminent but real collapse risk remains unmitigated after client notification and an unanswered regulatory call, the public welfare obligation displaces any residual deference to client preference about further escalation. Client B's potential preference against further disclosure cannot lawfully or ethically cap Engineer A's escalation duty once the regulatory channel has gone silent.

Does the Risk Threshold Calibration principle - which counsels proportionate rather than maximum escalation for non-imminent risks - conflict with the Persistent Escalation Obligation triggered by the county building official's non-response, and how should Engineer A resolve the tension between measured response and the duty to keep pressing until the hazard is addressed?

AnalyticalIn response to Q202: The tension between proportional escalation for non-imminent risks and the persistent escalation obligation triggered by the county building official's non-response is resolved by recognizing that proportionality governs the form and sequence of escalation, not its ultimate necessity. For a non-imminent risk, proportionality counsels against immediately deploying the full-bore, multi-agency campaign appropriate for an imminent collapse - as seen in BER Case 00-5 - and instead favors a graduated, deadline-conditioned approach modeled on BER Case 07-10. However, proportionality does not permit Engineer A to stop escalating simply because the risk is non-imminent. The county building official's failure to return the phone call is precisely the trigger that advances Engineer A to the next step in the graduated escalation sequence: a written notification to the official's supervisor, the fire marshal, or other agencies with jurisdiction. The proportionality principle shapes the pace and formality of escalation; the persistent escalation obligation ensures that non-response at one level does not terminate the process. The two principles are therefore complementary rather than conflicting when properly sequenced.
AnalyticalThe interaction between the Risk Threshold Calibration principle and the Persistent Escalation Obligation reveals that proportionality governs the form and pace of escalation, not whether escalation occurs at all. Because the collapse risk was non-imminent rather than imminent, Engineer A was not required to pursue the full-bore, multi-agency, physical-closure campaign demanded by BER Case 00-5's bridge scenario. However, proportionality does not mean passivity: the Persistent Escalation Obligation, activated by the county building official's non-response, required Engineer A to advance to the next available authority - the official's supervisor, the fire marshal, or any other agency with jurisdiction - in writing. The case thus teaches that the imminent/non-imminent distinction calibrates the intensity and urgency of escalation but does not create a threshold below which escalation becomes optional. A graduated, deadline-conditioned written escalation chain is the proportionate response to a non-imminent risk combined with regulatory non-response, and stopping at a single unanswered phone call falls below even the proportionate minimum.

Does the Scope-of-Work Limitation as Incomplete Defense principle conflict with the Multi-Credential Competence Activation Obligation in determining how far Engineer A's structural analysis should extend: if Engineer A's forensic engagement was limited to fire origin and cause, does invoking structural expertise simultaneously expand both the duty to disclose and the duty to perform a thorough structural evaluation beyond what a preliminary assessment provides?

AnalyticalIn response to Q203: The scope-of-work limitation of Engineer A's fire investigation engagement cannot serve as a complete defense against the obligation to disclose and act on the structural deficiency, but it does shape the extent of the structural analysis Engineer A is obligated to perform. The multi-credential competence activation obligation means that Engineer A's status as a licensed structural engineer - not merely a fire investigator - activates a professional duty to assess and disclose structural hazards that come within Engineer A's observation and competence during the engagement. However, this activation does not automatically require Engineer A to conduct a full, fee-bearing structural engineering investigation beyond the scope of the fire investigation contract. What it does require is: (1) disclosure of the observed structural concern to Client B and relevant authorities, (2) a preliminary assessment sufficient to characterize the nature and approximate severity of the risk, and (3) a recommendation that a comprehensive structural evaluation be performed by a qualified engineer. Engineer A is not ethically required to perform that comprehensive evaluation without a separate engagement, but Engineer A is ethically prohibited from treating the scope limitation as a reason to remain silent about a hazard that professional competence has identified.
AnalyticalThe interaction between the Scope-of-Work Limitation as Incomplete Defense principle and the Multi-Credential Competence Activation Obligation establishes a compounding duty structure: when an engineer possesses structural expertise and exercises it - even incidentally during a fire investigation - the contractual scope of the engagement cannot insulate that engineer from the ethical consequences of what the structural expertise reveals. Engineer A's preliminary structural assessment, however labeled, constituted a professional judgment by a licensed structural engineer. That judgment activated both the Incidental Observation Disclosure Obligation and the Written Documentation Requirement simultaneously. The case further teaches that the Written Documentation Requirement does not conflict with proportional escalation for non-imminent risks; rather, written documentation is precisely the proportionate tool for non-imminent risks because it creates an accountable record that survives the informality of a phone call, ensures the hazard is not lost in bureaucratic non-response, and satisfies the engineer's duty under NSPE Code Section II.1.a to notify when judgment is effectively overruled by inaction. The preliminary nature of the structural assessment may appropriately qualify the epistemic confidence expressed in written notifications, but it does not reduce the obligation to make them.

Does the Written Documentation Requirement - which demands that safety notifications be memorialized in writing - conflict with the Proportional Escalation Obligation for non-imminent risks, in the sense that imposing a formal written escalation chain on a non-imminent hazard may be disproportionate, yet failing to document leaves the public unprotected if the verbal-only notification is ignored as it was in BER Case 07-10?

AnalyticalIn response to Q204: The written documentation requirement and the proportional escalation obligation for non-imminent risks are not genuinely in conflict - they operate on different dimensions of the same duty. Proportionality addresses the intensity and urgency of escalation; the written documentation requirement addresses the form that escalation must take to be effective and verifiable. BER Case 07-10 demonstrates precisely why verbal-only notification is insufficient even for non-imminent risks: Engineer A in that case made only a verbal communication to the town supervisor, and the Board found that obligation unfulfilled because there was no written record and no confirmed follow-up. The lesson is that written documentation is not a disproportionate formality - it is the minimum standard of care for any safety notification that must survive the test of non-response or denial. A written escalation to the county building official's supervisor or the fire marshal is not disproportionate to a non-imminent structural collapse risk; it is the appropriate and proportionate response to a situation where a verbal phone call has already been ignored. The written documentation requirement therefore reinforces rather than conflicts with proportional escalation.
Theoretical (4)

From a deontological perspective, did Engineer A fulfill their categorical duty to protect public safety by stopping at a verbal phone call to the county building official, or does the duty to hold public welfare paramount impose an unconditional obligation to escalate in writing regardless of the non-imminent nature of the collapse risk?

AnalyticalIn response to Q301: From a deontological perspective, Engineer A did not fulfill the categorical duty to protect public safety by stopping at a single unanswered phone call. The NSPE Code's mandate to hold public welfare paramount functions as a near-categorical rule: it does not permit an engineer to discharge the duty through a single good-faith gesture that produces no protective outcome. Kant's categorical imperative, applied to professional engineering ethics, would ask whether a maxim of 'notify once verbally and then stop' could be universalized without undermining the entire system of public safety protection that engineering licensure is designed to provide. It cannot. If every engineer treated a single unanswered phone call as sufficient discharge of the public safety duty, the duty would be rendered meaningless in precisely the cases where it matters most - those where responsible authorities are unresponsive. The non-imminent nature of the collapse risk affects the urgency and form of the duty's discharge, but it does not convert the categorical obligation into a discretionary one. Engineer A's duty to escalate in writing to supervisory and alternative regulatory authorities is unconditional once the initial notification has been ignored.

From a consequentialist perspective, did Engineer A's decision to limit escalation to a single unanswered phone call produce the best achievable outcome for public safety, given that the building retained a certificate of occupancy and the collapse risk remained unmitigated, and would a written multi-agency escalation campaign have produced a meaningfully safer outcome at proportionate cost?

AnalyticalIn response to Q302: From a consequentialist perspective, Engineer A's decision to limit escalation to a single unanswered phone call produced a clearly suboptimal outcome for public safety. The building retained a certificate of occupancy, the structural deficiency remained unaddressed, and the collapse risk was unmitigated. The counterfactual outcomes of a written multi-agency escalation campaign are meaningfully better: written notification to the county official's supervisor, the fire marshal, or state building authorities would have created an official record, imposed accountability on regulatory actors, and substantially increased the probability that the structural deficiency would be formally reviewed and remediated. The costs of that escalation - primarily Engineer A's time and the potential for regulatory friction with Client B - are modest compared to the benefit of reducing the probability of structural collapse and the associated harm to occupants and the public. A consequentialist calculus therefore strongly supports the Board's conclusion that Engineer A was obligated to pursue written escalation. The non-imminent characterization of the risk reduces the urgency of the escalation but does not change the direction of the cost-benefit analysis.

From a virtue ethics perspective, did Engineer A demonstrate the professional integrity and moral courage expected of a competent structural engineer by recommending bracing to the owners and making a single phone call, or does genuine professional virtue require persistent, documented advocacy until a responsible authority acknowledges and acts on the structural deficiency?

AnalyticalIn response to Q303: From a virtue ethics perspective, Engineer A's actions - recommending bracing to the owners and making a single phone call - reflect the beginning of professional virtue but fall short of its full expression. A virtuous professional engineer, characterized by integrity, moral courage, and genuine commitment to public welfare, would not treat an unanswered phone call as the end of the matter when a structural hazard remains unaddressed. Virtue ethics asks not merely what rules require but what a person of excellent professional character would do. Such a person would recognize that the phone call's failure to produce a response is not a discharge of responsibility but a signal that more persistent and formal action is required. The virtue of moral courage is particularly relevant: escalating in writing to supervisory authorities, potentially over the objection of Client B, requires a willingness to accept professional friction in service of a higher obligation. Engineer A's preliminary assessment and initial notifications demonstrate competence and good faith, but genuine professional virtue requires persistent, documented advocacy until a responsible authority acknowledges and commits to addressing the structural deficiency.

From a deontological perspective, does Engineer A's dual role as forensic fire investigator and licensed structural engineer create a non-waivable duty to act on incidentally discovered structural hazards, such that the scope-of-work limitation of the fire investigation contract cannot serve as a moral or professional defense for inaction, and how does this duty interact with the faithful agent obligation owed to Client B?

AnalyticalIn response to Q304: Engineer A's dual role as forensic fire investigator and licensed structural engineer creates a non-waivable duty to act on incidentally discovered structural hazards, and the scope-of-work limitation of the fire investigation contract cannot serve as a moral or professional defense for inaction. The NSPE Code's competence provision in Section I.2 and the public welfare paramount principle in Section I.1 operate independently of contractual scope definitions. When Engineer A's structural engineering competence is activated by the observation of a structural deficiency - regardless of the engagement's primary purpose - the professional duty to disclose and escalate attaches. The faithful agent obligation to Client B is satisfied by prompt notification, but it does not extend to suppressing the structural concern from regulatory authorities. The interaction between the scope limitation and the faithful agent duty is therefore asymmetric: the scope limitation constrains what Engineer A is contractually obligated to investigate and report to Client B as a deliverable, but it does not constrain what Engineer A is ethically obligated to disclose to public authorities as a licensed professional. The dual-role context thus expands rather than contracts Engineer A's disclosure obligations.
Counterfactual (4)

If Engineer A had immediately followed the unanswered phone call with a written notification to the county building official's supervisor and the fire marshal, would the certificate of occupancy have been suspended and the collapse risk mitigated before the building was reoccupied, and does the absence of that written escalation constitute a breach of Engineer A's ethical obligations regardless of the non-imminent nature of the risk?

AnalyticalIn response to Q401: If Engineer A had immediately followed the unanswered phone call with written notification to the county building official's supervisor and the fire marshal, the probability of the certificate of occupancy being suspended and the collapse risk being mitigated before reoccupancy would have been substantially higher. Written notification creates an official record that demands a documented response, imposes accountability on supervisory officials, and activates the fire marshal's independent authority to inspect and act. Whether the certificate would definitively have been suspended cannot be determined with certainty, but the absence of written escalation removes the most effective mechanism available to Engineer A for compelling regulatory action. The absence of that written escalation does constitute a breach of Engineer A's ethical obligations under the NSPE Code, regardless of the non-imminent nature of the risk. The non-imminent characterization affects the urgency and form of escalation but does not eliminate the obligation. An engineer who identifies a structural hazard, notifies the client, makes a single unanswered phone call, and then stops has not discharged the duty to hold public welfare paramount - particularly when the building retains a certificate of occupancy that affirmatively misleads occupants about its safety.

What if the county building official had returned Engineer A's phone call but refused to revoke the certificate of occupancy, citing the prior inspection as sufficient - would Engineer A's ethical obligations have required escalation to the fire marshal, state building authority, or other agencies, and how does the BER 07-10 precedent of deadline-conditioned escalation inform what Engineer A should have done next?

AnalyticalIn response to Q402: If the county building official had returned Engineer A's call but refused to revoke the certificate of occupancy, citing the prior inspection as sufficient, Engineer A's ethical obligations would have required escalation to the fire marshal, state building authority, or other agencies with jurisdiction. A responsive but dismissive official does not terminate Engineer A's escalation obligation any more than a non-responsive one does. The BER 07-10 precedent of deadline-conditioned escalation is instructive: in that case, the Board held that Engineer A should have given the town supervisor a reasonable deadline to act and, upon non-compliance, escalated to the county and state building officials. The same logic applies here: if the county building official affirmatively refuses to act, Engineer A should document that refusal in writing, advise the official of the structural basis for the concern, and then escalate to supervisory and alternative regulatory authorities. The official's prior inspection and certificate of occupancy do not constitute a final and unreviewable safety determination; they are administrative actions that can be revisited when new professional evidence of structural deficiency is presented by a licensed engineer.

What if Client B had explicitly instructed Engineer A not to contact any government authorities about the structural deficiency, invoking confidentiality - would that instruction have relieved Engineer A of the obligation to notify the county building official and escalate further, or does the public welfare paramount principle override any client-imposed confidentiality constraint in a case involving structural collapse risk?

AnalyticalIn response to Q403: If Client B had explicitly instructed Engineer A not to contact any government authorities about the structural deficiency, invoking confidentiality, that instruction would not have relieved Engineer A of the obligation to notify the county building official and escalate further. The NSPE Code's confidentiality provisions do not extend to suppressing information about structural hazards that endanger public safety. The confidentiality non-applicability principle is well-established in engineering ethics: an engineer cannot be bound by client confidentiality to remain silent about conditions that pose a risk to the life, health, or safety of the public. A client instruction to withhold safety-critical information from regulatory authorities is not a legitimate exercise of the client's authority over the professional relationship - it is a request that Engineer A breach a higher-order professional duty. Engineer A would be obligated to inform Client B that the instruction cannot be followed, to document that communication, and to proceed with notification to the county building official and, upon non-response, to supervisory and alternative regulatory authorities. The public welfare paramount principle overrides any client-imposed confidentiality constraint in a case involving structural collapse risk.

If the structural instability Engineer A discovered had posed an imminent rather than non-imminent collapse risk, how would Engineer A's escalation obligations have differed - would the BER 00-5 precedent of full-bore, multi-agency escalation and physical closure measures have applied, and does the non-imminent characterization in the current case represent a meaningful ethical distinction or merely a difference in urgency rather than in the underlying duty?

AnalyticalIn response to Q404: If the structural instability Engineer A discovered had posed an imminent rather than non-imminent collapse risk, the BER 00-5 precedent of full-bore, multi-agency escalation and physical closure measures would have applied directly. In BER 00-5, the Board held that Engineer A was obligated to erect physical barricades, close the bridge to traffic, resist public pressure to reopen it, and escalate through multiple governmental channels simultaneously - all because the collapse risk was imminent and the consequences catastrophic. In the current case, the non-imminent characterization does represent a meaningful ethical distinction, but it is a distinction in urgency and form rather than in the underlying duty. The underlying duty - to hold public welfare paramount and to escalate until a responsible authority acts - is identical in both cases. What changes is the pace, the sequence, and the proportionality of the escalation response. An imminent risk demands immediate, simultaneous, multi-agency action and physical intervention if necessary. A non-imminent risk demands graduated, documented, deadline-conditioned escalation through the regulatory hierarchy. Both demands are ethically obligatory; neither permits Engineer A to stop at a single unanswered phone call.
Decisions & Arguments (6)
View Extraction

After the county building official fails to return Engineer A's phone call regarding a non-imminent but real structural collapse risk, what escalation actions does Engineer A's public safety obligation require?

Options considered:
O1 Follow up the unanswered phone call with written notification to the county building official's supervisor and the fire marshal, documenting the structural concern, the preliminary assessment findings, and the prior unanswered contact, while continuing to work collaboratively with Client B toward remediation Board's choice
O2 Send a written follow-up letter to the same county building official reiterating the structural concern and requesting a response within a defined deadline, deferring escalation to supervisory or alternative agencies unless that deadline passes without acknowledgment
O3 Treat the unanswered phone call as sufficient initial discharge of the reporting obligation for a non-imminent risk, document the call in Engineer A's own records, and await further developments, such as owner refusal to brace or building reoccupancy, before escalating further
Argument structure:
Warrants

The Persistent Escalation Obligation requires that an unanswered initial report advance Engineer A to the next regulatory level. The Written Documentation Requirement mandates that safety notifications be memorialized in writing to create an accountable record. The Post-Unresponsive-Official Multi-Agency Escalation Obligation requires contact with the official's supervisor, the fire marshal, or other agencies with jurisdiction. The Proportional Escalation Obligation calibrated to non-imminent risk counsels a graduated, deadline-conditioned approach rather than a simultaneous multi-agency blitz.

Rebuttals

The non-imminent nature of the collapse risk could be read to limit the escalation duty: if the hazard is not immediate, a single good-faith notification might be treated as proportionate. The preliminary character of Engineer A's structural assessment introduces epistemic uncertainty that could be argued to defer formal escalation pending a more definitive evaluation. The county building official's prior issuance of a certificate of occupancy might be read as an implicit prior review that reduces the urgency of further escalation.

Grounds

Engineer A verbally notified the county building official of a structural collapse risk; the official did not return the call; the building retains a certificate of occupancy; the collapse risk remains unmitigated; the building owners were advised to install bracing but no confirmed remediation occurred.

Post-Unresponsive-Official Written Follow-Up and Escalation Obligation Engineer A Non-Imminent Collapse Proportionate Response Calibration

When Client B has been verbally notified of the structural deficiency but may object to further regulatory escalation that could trigger costly remediation or liability, does Engineer A's faithful agent duty constrain the public safety escalation obligation?

Options considered:
O1 Inform Client B that written escalation to supervisory regulatory authorities is professionally required regardless of client preference, document that communication, and proceed with written notification to the county building official's supervisor and fire marshal while inviting Client B to participate constructively in the escalation process Board's choice
O2 Work collaboratively with Client B to pursue voluntary remediation, including engaging a structural engineer for a definitive evaluation and implementing the recommended bracing, before escalating to supervisory regulatory authorities, treating client collaboration as the preferred first path and regulatory escalation as a subsequent step if collaboration fails
O3 Treat the faithful agent duty as requiring deference to Client B's preferences on further escalation given the non-imminent nature of the risk, limit further action to written documentation of the concern in Engineer A's own records, and advise Client B in writing of the structural risk and the recommendation to engage a structural engineer, without independently contacting supervisory regulatory authorities absent Client B's consent
Argument structure:
Warrants

The Public Welfare Paramount principle (NSPE Code Section I.1) establishes a hierarchical ceiling above which client loyalty cannot operate. The Faithful Agent Notification Obligation is satisfied by prompt notification to Client B, after which the client's preferences cannot veto independent public safety obligations. The Confidentiality Non-Applicability principle establishes that professional confidentiality does not bar disclosure of structural hazards to regulatory authorities. The Non-Imminent Structural Risk Persistent Client Collaboration Obligation recognizes that client collaboration and regulatory escalation are complementary, not alternative, duties.

Rebuttals

The non-imminent nature of the collapse risk creates genuine uncertainty about whether the public welfare paramount principle overrides client deference at this threshold: if the risk is real but not immediate, a reasonable argument exists that the faithful agent duty to work within the client relationship should be exhausted before unilateral regulatory escalation. Client B's notification and the bracing recommendation could be read as having discharged Engineer A's immediate public safety duty, leaving further escalation as a matter of professional judgment rather than categorical obligation.

Grounds

Engineer A immediately advised Client B of the structural instability and called the county building official. Client B was notified verbally. The county building official did not respond. The collapse risk remains unmitigated. Client B, as the party who retained Engineer A and who bears financial and legal exposure, may prefer that Engineer A not escalate further to supervisory or alternative regulatory authorities.

Faithful Agent Immediate Structural Hazard Notification Obligation Confidentiality Non-Applicability to Public Danger Disclosure

Does the preliminary and incidental nature of Engineer A's structural assessment, made during a fire investigation engagement rather than a formal structural engineering engagement, affect the threshold at which disclosure and escalation to regulatory authorities become obligatory?

Options considered:
O1 Disclose the preliminary structural findings in writing to Client B and the county building official immediately, clearly qualifying the assessment as preliminary, recommending that a comprehensive structural evaluation be commissioned, and escalating to supervisory authorities upon the official's non-response, without waiting for a definitive evaluation before initiating disclosure Board's choice
O2 Recommend to Client B that a separate structural engineering engagement be commissioned to produce a definitive assessment before notifying regulatory authorities, on the grounds that a preliminary finding by an engineer retained for a different scope does not yet constitute a sufficient professional basis for regulatory escalation
O3 Include the structural observations as a noted finding in the fire investigation report delivered to Client B, flagging the concern for Client B's attention and recommending further evaluation, while treating the scope limitation of the fire investigation engagement as precluding independent regulatory notification absent a separate structural engineering retainer
Argument structure:
Warrants

The Multi-Credential Competence Activation Obligation establishes that when an engineer exercises licensed structural judgment, even incidentally, the full suite of public safety obligations of that discipline is activated. The Scope-of-Work Limitation as Incomplete Defense principle establishes that a contractual scope limitation cannot justify silence about hazards already identified through professional competence. The Incidental Observation Disclosure Obligation requires disclosure of observed safety risks to the client and appropriate public authorities. The preliminary nature of the assessment imposes an epistemic honesty obligation, findings must be communicated as preliminary, but does not eliminate the disclosure duty.

Rebuttals

The scope-of-work limitation of the fire investigation contract creates a genuine argument that Engineer A's structural observations were outside the engagement's deliverables and that a formal structural engineering engagement would be needed before regulatory notification is appropriate. The preliminary characterization of the assessment could be read to mean that Engineer A's findings do not yet rise to the level of professional certainty required to trigger regulatory disclosure, particularly given that the county building official previously reviewed and approved the modifications.

Grounds

Engineer A was retained for fire origin and cause investigation. During that investigation, Engineer A, who also holds structural engineering credentials, observed structural instability and concluded on a preliminary basis that recent structural modifications caused roof sag and outward wall lean due to insufficient lateral restraint. The assessment was described as preliminary. The building had been issued a certificate of occupancy following the modifications.

Multi-Credential Structural Competence Activation in Fire Investigation Obligation Scope-of-Work Non-Shield for Structural Safety Disclosure Obligation

Should Engineer A escalate structural safety concerns beyond the county building official who issued the certificate of occupancy, or should Engineer A defer to that official's prior approval and limit escalation accordingly?

Options considered:
O1 Because the building official who issued the certificate of occupancy may be compromised by his own prior approval, Engineer A should escalate in writing directly to that official's supervisor and the fire marshal, explicitly noting that the building retains a certificate of occupancy issued after the deficient modifications. Board's choice
O2 Treat the certificate of occupancy as neither heightening nor diminishing the escalation obligation, and direct written notice of the structural findings to the same county building official, requesting a formal re-inspection and leaving further escalation to that official's discretion.
O3 Treat the certificate of occupancy as evidence that the county building official previously reviewed and accepted the structural modifications, and defer further escalation until a definitive engineering assessment confirms that the official's prior judgment was in error.
Argument structure:
Warrants

The Certificate of Occupancy Authority Re-Notification Obligation establishes that the official who granted occupancy approval bears regulatory responsibility for the building's continued safe use and is the appropriate first-line authority for remedial action. The Persistent Escalation Obligation requires escalation beyond a non-responsive first-line authority. The certificate of occupancy creates a compounded public safety risk because occupants are affirmatively misled about the building's safety, heightening rather than diminishing the escalation obligation. The official's apparent failure to detect the deficiency during the prior inspection is itself a reason to escalate to supervisory authorities.

Rebuttals

The certificate of occupancy could be read as evidence that the county building official previously reviewed and implicitly approved the structural modifications, creating a reasonable argument that Engineer A's preliminary contrary assessment should defer to the official's prior professional judgment rather than triggering escalation that second-guesses that judgment. If the official reviewed the modifications with knowledge of their structural implications, the certificate may represent a considered engineering determination that Engineer A's preliminary assessment has not yet rebutted with sufficient certainty.

Grounds

Following structural modifications to the building, the county building official issued a certificate of occupancy. Engineer A subsequently identified structural deficiencies, roof sag and outward wall lean due to insufficient lateral restraint, arising from those same modifications. The county building official did not return Engineer A's phone call. The certificate of occupancy remains in force, creating an affirmative public signal that the building is safe.

Certificate of Occupancy Authority Re-Notification After Structural Modification Discovery Obligation Post-Certificate-of-Occupancy Structural Safety Concern

When the building owners decline to implement Engineer A's bracing recommendation and the county building official has not responded, does the combination of owner inaction and regulatory non-response independently require Engineer A to escalate to additional authorities, and how does the non-imminent nature of the risk calibrate that obligation?

Options considered:
O1 Document the owners' refusal to implement bracing in writing, advise the owners in writing of the continued structural risk and their responsibility for it, and immediately escalate in writing to the county building official's supervisor and the fire marshal, treating the combination of owner refusal and official non-response as exhausting all direct remedies and requiring multi-agency regulatory escalation Board's choice
O2 Re-engage Client B and the building owners collaboratively to pursue voluntary remediation, including commissioning a definitive structural evaluation and presenting its findings to the owners, before escalating to supervisory regulatory authorities, treating the owners' initial refusal as a starting point for negotiation rather than a final determination
O3 Treat the owners' refusal as a property owner's exercise of authority over their own building in the context of a non-imminent risk, document the refusal and Engineer A's recommendation in writing for Engineer A's own records, and limit further action to a written follow-up to the county building official, without escalating to supervisory or alternative regulatory authorities absent evidence that the risk has become more imminent
Argument structure:
Warrants

The Persistent Escalation Obligation requires that Engineer A continue pursuing resolution when no responsible party has acted. The Non-Imminent Structural Risk Persistent Client Collaboration Obligation recognizes that client collaboration and regulatory escalation are complementary duties. The Proportional Escalation Obligation calibrated to imminence and breadth of risk requires that the combination of owner refusal and official non-response be assessed together, the cumulative failure of all available direct remedies advances the escalation obligation even if neither factor alone would have done so. The Public Welfare Paramount principle establishes that owner refusal is not a private business decision when it leaves a known public hazard unmitigated.

Rebuttals

The non-imminent nature of the collapse risk creates a genuine argument that owner refusal, while concerning, does not independently trigger mandatory regulatory escalation beyond what the official non-response already requires, the risk calibration principle counsels proportionate rather than maximum response, and the owners' refusal may be a business judgment that falls within their authority over their own property absent an imminent danger. The combination of factors might be read as requiring only that Engineer A document the refusal and the unmitigated risk in writing, rather than launching a multi-agency escalation campaign.

Grounds

Engineer A recommended that the building owners install bracing to address the structural instability. The owners declined to implement the recommendation. The county building official did not return Engineer A's phone call. The collapse risk remains unmitigated. The building retains a certificate of occupancy. No responsible party, owner or regulatory authority, has taken corrective action.

Post-Unresponsive-Official Multi-Agency Escalation Obligation Proportional Escalation Obligation Calibrated to Imminence and Breadth of Risk

Should Engineer A send written documentation of the structural concern to the county building official immediately after the unanswered phone call, or is some lesser form of documentation proportionate to a hazard that is real but not immediately life-threatening?

Options considered:
O1 Written documentation is the baseline minimum standard of care whenever a verbal notification has been ignored, regardless of imminence. Engineer A must send a written summary of the structural findings and prior verbal contact to the county building official without further delay, creating an accountable record that cannot be denied or misunderstood. Board's choice
O2 Treat the verbal phone call as proportionate to the non-imminent nature of the risk for now, and prepare a written internal memorandum documenting the preliminary findings and the unanswered call, escalating to external written notice only if the official remains unresponsive after a defined waiting period.
O3 Treat the verbal notification to the county building official as sufficient given the non-imminent character of the structural risk, and confine written documentation to the fire investigation report delivered to Client B, leaving it to Client B to decide whether to forward concerns to regulatory authorities.
Argument structure:
Warrants

The Written Documentation Requirement establishes that safety notifications must be memorialized in writing to create an accountable record that cannot be misunderstood, ignored, or denied. BER Case 07-10 directly held that verbal-only notification was insufficient and that written follow-up was required. Written documentation is not a disproportionate formality for non-imminent risks, it is precisely the proportionate tool because it creates regulatory traction that survives the informality of a phone call. The Proportional Escalation Obligation governs the intensity and urgency of escalation, not whether documentation is required.

Rebuttals

The Proportional Escalation Obligation for non-imminent risks could be read to counsel against imposing a formal written escalation chain on a hazard that is real but not immediate: if the risk does not require emergency action, a verbal notification might be treated as proportionate to the level of urgency. The preliminary nature of Engineer A's assessment could further support deferring formal written escalation until a more definitive structural evaluation is available, so that written notifications to regulatory authorities are based on findings of sufficient certainty to warrant formal administrative action.

Grounds

Engineer A verbally notified Client B of the structural instability and made a single phone call to the county building official. The official did not return the call. No written documentation of the structural concern was sent to the county building official, the official's supervisor, or any other regulatory authority. The BER Case 07-10 precedent found verbal-only communication with a town supervisor insufficient and required written follow-up.

Post-Verbal-Notification Written Structural Safety Confirmation Obligation Risk Threshold Calibration in Public Safety Reporting
10 sequenced 5 actions 5 events
Case timeline
A fire breaks out at a building owned by Client B, triggering the need for an engineering investigation. This exogenous event sets the entire case in motion.
Upon observing structural instability during a fire investigation, Engineer A voluntarily expanded the scope of work beyond the contracted fire origin-and-cause investigation to perform a preliminary structural assessment of the building.
Fulfills (3)
  • NSPE Code obligation to hold public safety, health, and welfare paramount
  • Obligation to use professional knowledge and skill in the public interest when a hazard is observed
  • Obligation to act on competence. Engineer A was also a structural engineer and thus qualified to perform the assessment
During the fire investigation, Engineer A discovers sagging roof and outward-leaning walls, indicating serious structural instability likely caused by recent construction modifications. This discovery transforms a routine fire investigation into a public safety emergency.
The previously issued certificate of occupancy by the county building official is rendered effectively void by Engineer A's findings of structural instability, revealing a failure of the regulatory certification process. This is not a formal administrative act but a factual condition that undermines the legal and safety assurance the certificate was meant to provide.
After concluding the preliminary structural investigation, Engineer A immediately and verbally advised Client B of the structural danger, including the risk of eventual building collapse due to insufficient lateral restraint from recent construction modifications.
Fulfills (3)
  • Obligation to notify the client of discovered hazards affecting the safety of the structure
  • Obligation to be transparent and forthright with the client about findings material to public safety
  • NSPE Code obligation to inform relevant parties of safety risks
Violates (1)
  • Obligation to document safety notifications in writing: verbal-only notification, as highlighted in BER 07-10, is insufficient to create an enforceable and durable record of the warning
Engineer A contacted the county building official by phone to report the structural hazard, but did not escalate further after the official failed to return the call, leaving the regulatory notification at a single unanswered attempt.
At stake (2)
  • Obligation to escalate when the initial regulatory contact is unresponsive, the Board concluded Engineer A should have contacted the county official's supervisor, the fire marshal, or other agencies after the unanswered call
  • Obligation to persist in pursuing corrective action until the safety risk is adequately addressed
Fulfills (2)
  • Initial obligation to notify the authority having jurisdiction over the building's safety
  • Obligation to report conditions that endanger public safety to competent authorities (NSPE Code Section I.1 and III.2)
Violates (1)
  • Obligation to document the notification attempt in writing
Engineer A recommended to the building owners that they brace the building to prevent collapse, providing a specific remediation action to mitigate the identified structural risk while awaiting regulatory or other corrective action.
Fulfills (3)
  • Obligation to provide professional guidance to mitigate identified safety risks
  • Obligation to act in the interest of public safety by recommending protective measures
  • Obligation to be forthright with clients and owners about steps needed to address safety hazards (NSPE Code Section III.2)
Violates (2)
  • Obligation to document the recommendation in writing to create a durable record
  • Obligation to follow up to confirm whether the bracing recommendation was implemented
After Engineer A calls the county building official to report the structural instability, the official does not return the call, leaving the safety concern unaddressed at the regulatory level. This non-response creates a critical gap in the safety response chain.
After the county building official failed to return Engineer A's phone call, Engineer A made no further attempt to escalate the structural safety concern to the official's supervisor, the fire marshal, or any other agency with jurisdictional authority, effectively ending active regulatory pursuit of the matter.
Violates (4)
  • Obligation to continue pursuing corrective action until the public safety risk is adequately addressed (NSPE Code Section I.1)
  • Obligation to escalate to higher or alternative authorities when the initial regulatory contact is unresponsive
  • Obligation not to permit professional duties to be subordinated to the inaction of others when public safety is at stake
  • NSPE Code obligation to notify appropriate authorities and persist in doing so when the safety of the public is at risk
Despite Engineer A's verbal notification to Client B, call to the county official, and bracing recommendation, the structural collapse risk remains unaddressed: the county has not responded, bracing has not been confirmed as implemented, and no formal written documentation has been issued. The hazard persists in an unresolved state.
Narrative (2 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 A, a licensed structural engineer retained by Client B to investigate the origin and cause of a fire at a commercial building. During your fire investigation, you observe that the building is structurally unstable, with a sagging roof and outward-leaning walls consistent with insufficient lateral restraint. Your preliminary assessment suggests that recent construction modifications to the building are the likely cause of these conditions. You have notified Client B verbally and called the county building official, who has not returned your call. You have also recommended that the building owners brace the structure to prevent collapse, though no imminent collapse is expected at this time. The county previously issued a certificate of occupancy for the building following the modifications you now identify as the source of the deficiency. The professional decisions ahead involve your obligations to your client, to regulatory authorities, and to public safety.

Main characters (2)

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.

Client B Roles in this case: Building Safety Investigation Client

The obligation to collaborate with the client on non-imminent structural risks pulls toward a measured, client-centered process that respects the owner's agency and timeline. However, the constraint requiring persistent escalation beyond an unresponsive county official pushes the engineer toward unilateral action that may bypass or undermine the collaborative relationship. Fulfilling the escalation duty may fracture client trust and exceed the client's consent, while deferring to collaboration may leave a structural risk unaddressed if the official remains unresponsive. The engineer is caught between honoring the client relationship and fulfilling an independent public-safety duty that operates outside that relationship.

Engineer A Roles in this case: Forensic Building Investigation Engineer(BER 00-5) Local Government Bridge Safety Engineer(BER 07-10) Post-Sale Safety Notifying Engineer(Current Case) Forensic Building Investigation Engineer

The faithful-agent obligation demands immediate notification of a structural hazard to protect public safety, which may logically point toward notifying the county building official or other authorities without delay. The constraint, however, requires that the new building owner be notified before any escalation to official bodies. These two directives create a sequencing dilemma: strict compliance with the priority-notification constraint could introduce a time lag before authorities are engaged, during which the hazard persists unmitigated. Conversely, bypassing the new owner to notify officials immediately may violate the owner's right to be informed first and damage the engineer's faithful-agent duty to that client. The tension is sharpest when the new owner is difficult to reach quickly.

Attaches to role: Forensic Building Investigation Engineer

The obligation to collaborate with the client on non-imminent structural risks pulls toward a measured, client-centered process that respects the owner's agency and timeline. However, the constraint requiring persistent escalation beyond an unresponsive county official pushes the engineer toward unilateral action that may bypass or undermine the collaborative relationship. Fulfilling the escalation duty may fracture client trust and exceed the client's consent, while deferring to collaboration may leave a structural risk unaddressed if the official remains unresponsive. The engineer is caught between honoring the client relationship and fulfilling an independent public-safety duty that operates outside that relationship.

Attaches to role: Forensic Building Investigation Engineer

The scope-of-work non-shield obligation compels the engineer to disclose structural safety defects discovered incidentally, regardless of the contracted scope. Yet the proportionality constraint limits corrective action to responses calibrated to the actual level of risk — specifically, non-imminent collapse scenarios do not warrant the most aggressive interventions. This creates tension because the disclosure obligation, once triggered, may generate expectations of comprehensive remedial action from building owners or officials, while the proportionality constraint forbids over-reaction. The engineer must disclose fully without allowing that disclosure to cascade into disproportionate alarm or remedial overreach, a balance that is difficult to maintain in practice and may expose the engineer to criticism from both directions.

Attaches to role: Forensic Building Investigation Engineer

Tension between Post-Unresponsive-Official Written Follow-Up and Escalation Obligation and Engineer A Non-Imminent Collapse Proportionate Response Calibration

Attaches to role: Forensic Building Investigation Engineer

Other people involved in the case but not central to the opening narrative.

The scope-of-work non-shield obligation compels the engineer to disclose structural safety defects discovered incidentally, regardless of the contracted scope. Yet the proportionality constraint limits corrective action to responses calibrated to the actual level of risk — specifically, non-imminent collapse scenarios do not warrant the most aggressive interventions. This creates tension because the disclosure obligation, once triggered, may generate expectations of comprehensive remedial action from building owners or officials, while the proportionality constraint forbids over-reaction. The engineer must disclose fully without allowing that disclosure to cascade into disproportionate alarm or remedial overreach, a balance that is difficult to maintain in practice and may expose the engineer to criticism from both directions.

The faithful-agent obligation demands immediate notification of a structural hazard to protect public safety, which may logically point toward notifying the county building official or other authorities without delay. The constraint, however, requires that the new building owner be notified before any escalation to official bodies. These two directives create a sequencing dilemma: strict compliance with the priority-notification constraint could introduce a time lag before authorities are engaged, during which the hazard persists unmitigated. Conversely, bypassing the new owner to notify officials immediately may violate the owner's right to be informed first and damage the engineer's faithful-agent duty to that client. The tension is sharpest when the new owner is difficult to reach quickly.

The obligation to collaborate with the client on non-imminent structural risks pulls toward a measured, client-centered process that respects the owner's agency and timeline. However, the constraint requiring persistent escalation beyond an unresponsive county official pushes the engineer toward unilateral action that may bypass or undermine the collaborative relationship. Fulfilling the escalation duty may fracture client trust and exceed the client's consent, while deferring to collaboration may leave a structural risk unaddressed if the official remains unresponsive. The engineer is caught between honoring the client relationship and fulfilling an independent public-safety duty that operates outside that relationship.


These tensions did not map cleanly to a single character.

Tension between Faithful Agent Immediate Structural Hazard Notification Obligation and Confidentiality Non-Applicability to Public Danger Disclosure

Tension between Multi-Credential Structural Competence Activation in Fire Investigation Obligation and Scope-of-Work Non-Shield for Structural Safety Disclosure Obligation

Tension between Certificate of Occupancy Authority Re-Notification After Structural Modification Discovery Obligation and Post-Certificate-of-Occupancy Structural Safety Concern

Tension between Post-Verbal-Notification Written Structural Safety Confirmation Obligation and Risk Threshold Calibration in Public Safety Reporting

Tension between Post-Unresponsive-Official Multi-Agency Escalation Obligation and Proportional Escalation Obligation Calibrated to Imminence and Breadth of Risk

Opening States (10)
Unlicensed Bridge Inspector Practice - BER Case 00-5 Safety Closure Barrier Removal - BER Case 00-5 Post-Sale Structural Safety Concern - BER Case 07-10 Certificate of Occupancy Issued Despite Structural Concern - BER Case 07-10 Non-Imminent Structural Collapse Risk - BER Case 07-10 County Building Official Non-Response - Current Case Client Relationship - Engineer A and Client B Graduated Escalation Obligation - Non-Imminent Structural Collapse Public Safety at Risk - Structural Instability Multi-Authority Escalation Obligation - Bridge Case BER 00-5
Summary
  • Engineer A's duty to the client as faithful agent is not extinguished by public safety concerns but is sequenced beneath them, meaning client notification comes first but cannot serve as a terminal step when structural danger persists unaddressed.
  • Scope-of-work boundaries do not create an ethical shield against disclosure obligations when an engineer's multi-disciplinary credentials (here, structural competence activated during fire investigation) reveal an imminent or non-imminent but serious structural hazard.
  • When a responsible official is unresponsive to written follow-up, the escalation obligation activates as a proportionate, calibrated duty rather than an immediate maximalist response, reflecting the non-imminent nature of the collapse risk.