Step 4: Full View
Entities, provisions, decisions, and narrative
Full Entity Graph
Loading...Entity Types
Synthesis Reasoning Flow
Shows how NSPE provisions inform questions and conclusions - the board's reasoning chainThe 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.
Provisions (4)
View Extraction-
Confidentiality Non-Override Public Danger Engineer A Bridge Wall Defect
This provision governs confidentiality of client information, directly relevant to whether Engineer A could override confidentiality to report the wall defect.
-
Engineer A Bridge Case No Confidentiality Agreement Reduced Expectation Recognition
This provision on confidentiality is directly implicated by the obligation to recognize that no explicit confidentiality agreement reduced the agency's confidentiality expectation.
-
Engineer A Faithful Agent Client Loyalty Balance Bridge Wall Defect
This provision underlies the tension between protecting client confidentiality and disclosing safety findings that Engineer A was obligated to balance.
-
Passive Acquiescence Suppression Instruction Engineer A Wall Defect
This provision is relevant because the suppression instruction invoked client confidentiality interests that II.1.c. governs but does not permit when safety overrides apply.
-
Client Report Suppression Resistance Engineer A Bridge Wall Defect
This provision directly applies because VWX's instruction to omit the finding invoked confidentiality norms that II.1.c. addresses.
-
Comparative Case Precedent Distinguishing Engineer A Bridge vs Case 89-7
This provision is central to distinguishing the two cases since confidentiality obligations under II.1.c. differ based on whether a formal agreement exists.
-
Engineer A Case 89-7 Confidentiality Agreement Building Code Violation Reporting
This provision directly governed the confidentiality obligation in Case 89-7 that Engineer A was obligated to compare against the bridge wall defect case.
-
Verbally Report Defect to Client
Reporting to the client is permitted under this provision as it does not constitute unauthorized disclosure to outside parties.
-
Comply with Instruction to Omit from Final Report
This provision could be invoked to justify omission, but only if disclosure is not otherwise required by law or the Code.
-
Decline to Report to External Authorities
This provision governs the engineer's duty to withhold client information from external parties unless required by law or the Code.
-
Client-Loyalty vs. Public Safety Paramount Obligation Conflict
This provision directly governs the tension between Engineer A's duty not to disclose client information and the competing obligation to report safety concerns.
-
Client Chain Suppression of Wall Defect Finding
The provision addresses whether Engineer A may lawfully withhold the wall defect finding at client direction, as it permits disclosure when required by the Code.
-
Engineer A Verbal-Only Safety Report Without Written Documentation
The provision is relevant to what Engineer A may or may not disclose and in what form, bearing on the adequacy of verbal-only reporting.
-
Engineer A No External Escalation After Suppression
The provision provides the basis for whether Engineer A is authorized or required by the Code to escalate beyond the client chain despite confidentiality norms.
-
Engineer A Selective Omission in Final Bridge Inspection Report
The provision governs the limits of client-directed omission of facts from reports, permitting disclosure when the Code requires it.
-
No Confidentiality Agreement Between Engineer A and Client/Public Agency
The absence of a formal confidentiality agreement is relevant to the scope of the confidentiality duty this provision imposes.
-
Engineer A's Safety Observation Derived from Inspection Not Client Disclosure
The provision's applicability depends on whether the information was obtained through Engineer A's own observation rather than confidential client disclosure.
-
Inspection-Discovered Information Reduced Confidentiality Expectation. Engineer A Bridge Wall Defect vs. Case 89-7
II.1.c. governs confidentiality of facts and data, and this constraint modulates that confidentiality based on how the information was discovered.
-
Absence of Confidentiality Agreement Escalation Threshold Reduction. Engineer A Bridge Inspection
II.1.c. is the confidentiality provision whose threshold is directly reduced by the absence of an explicit confidentiality agreement.
-
Public Safety Paramount Over Confidentiality Engineer A Bridge Wall
II.1.c. contains the exception allowing disclosure when required by the Code, which is the basis for overriding confidentiality for public safety.
-
Confidentiality Non-Bar Safety Disclosure Engineer A Bridge Wall Defect
II.1.c. is the provision whose confidentiality bar is found inapplicable given the absence of an explicit agreement and independent discovery.
-
Inspection-Discovered Observation Confidentiality Modulation Engineer A Bridge
II.1.c. is directly modulated by the manner of discovery, as this constraint explains why the provision applies differently to independently observed versus client-confided information.
-
Faithful Agent Trustee Confidentiality Rationale. Engineer A VWX Bridge Engagement
II.1.c. is the code basis for the faithful agent confidentiality duty that constrained Engineer A's disclosure of client business information.
-
Client Confidentiality Reliance Factor Modulation. Inspection-Discovered vs. Client-Confided Bridge Wall Defect
II.1.c. is the confidentiality provision whose reliance factor is modulated depending on whether information was client-confided or independently discovered.
-
Client Suppression Instruction Non-Compliance Engineer A Wall Defect
II.1.c. permits disclosure when required by the Code, making compliance with a suppression instruction that violates the Code impermissible.
-
Confidentiality Non-Applicability to Public Danger Disclosure Bridge Wall Defect
II.1.c. establishes the confidentiality rule whose exception is directly invoked by this principle to permit disclosure of the wall defect.
-
Confidentiality Expectation Source-of-Information Distinction. Bridge Case vs. Case 89-7
II.1.c. is the confidentiality provision whose applicability is distinguished based on how Engineer A obtained the wall defect information.
-
Comparative Case Precedent Distinguishing. Bridge Case vs. Case 89-7
II.1.c. underlies the confidentiality analysis that the Board distinguishes across the four material factual differences between the two cases.
-
Faithful Agent Obligation. Engineer as Agent and Trustee of Client
II.1.c. codifies the faithful agent duty not to disclose client information without consent, which this principle directly invokes.
-
Public Welfare Paramount. Balancing Against Client Loyalty in Bridge Case
II.1.c. represents the client-loyalty confidentiality side of the balance the Board frames against public welfare obligations.
-
Client Report Suppression Prohibition Violated By Engineer A
II.1.c. is implicated because the suppression instruction attempts to use confidentiality norms to justify omitting safety-relevant findings.
-
Confidentiality Non-Applicability. Case 89-7 Building Code Violations Required Public Authority Notification
II.1.c. is the provision whose exception was applied in Case 89-7 to require reporting confirmed code violations despite confidentiality expectations.
-
Engineer A Bridge Sub-Consultant Inspector
Engineer A must navigate whether revealing the out-of-scope defect to authorities violates confidentiality obligations to VWX or is required by this Code.
-
Engineer A Corrective Action Monitoring Sub-Consultant
As sub-consultant, Engineer A is bound by confidentiality constraints when deciding whether to disclose observed defect information beyond the client chain.
-
VWX Architects and Engineers Prime Consultant
VWX must determine whether disclosing the structural defect information received from Engineer A to outside parties is permissible under confidentiality obligations to the public agency.
-
Engineer A Case 89-7 Confidentiality-Bound Building Sale Engineer
In Case 89-7, Engineer A operated under an explicit confidentiality agreement governing whether facts observed during inspection could be revealed without client consent.
-
Information Confined to Field Notes
The defect information being kept only in field notes relates to whether confidential data can be withheld from disclosure without proper authorization.
-
Suppression Instruction Issued
The instruction to suppress information tests the limits of II.1.c. since withholding safety-critical data may conflict with what the Code or law requires to be disclosed.
-
Client_Confidentiality_Public_Safety_Balancing_Framework_Instance
This provision is the direct source of the confidentiality duty that must be weighed against public safety obligations in this framework.
-
NSPE_Code_of_Ethics_Confidentiality_Provision
This entity directly cites the nondisclosure language of this provision as its source authority.
-
Agent_Trustee_Distinction_Framework_Instance
This provision underpins the rationale for engineer confidentiality as agents or trustees privy to client affairs.
-
Client-Confidentiality-vs-Public-Safety-Balancing-Framework
This provision establishes the confidentiality duty that Engineer A must weigh against his public safety obligation in this decision framework.
-
BER_Case_89-7
This precedent case applied confidentiality provisions analogous to II.1.c. in the context of a confidentiality agreement versus public safety.
-
BER_Case_97-5
This secondary precedent applied the same confidentiality versus public safety tension rooted in this provision.
-
BER-Case-Precedent-Bridge-Safety
Prior BER cases addressing client pressure to suppress findings invoke this provision as the source of the confidentiality obligation being tested.
-
Engineer A Confidentiality Non-Applicability Public Danger Bridge Wall
This provision governs when confidentiality obligations apply, directly requiring the capability to assess whether implied confidentiality bars disclosure of the wall defect.
-
Engineer A Client Suppression Instruction Recognition Wall Defect
This provision sets the boundary of confidentiality obligations, requiring recognition that a client suppression instruction cannot override lawful or Code-required disclosure.
-
Engineer A Passive Acquiescence Ethical Insufficiency Wall Defect
This provision requires engineers to understand when disclosure is authorized by the Code, making passive acquiescence to suppression a direct violation.
-
Engineer A Confidentiality Pre-emption Public Safety Bridge Wall
This provision establishes that Code-required disclosure pre-empts confidentiality, directly requiring the capability to recognize when public safety overrides client confidentiality.
-
Engineer A No-Confidentiality-Agreement Reduced Expectation Assessment Bridge Case
This provision's confidentiality protections are contextually reduced when no formal confidentiality agreement exists, requiring assessment of that reduced expectation.
-
Engineer A Faithful Agent Trustee Confidentiality Obligation Source Recognition Bridge Case
This provision is the source of the confidentiality obligation Engineer A must recognize and balance against Code-required disclosure duties.
-
Engineer A Passive Acquiescence Suppression Instruction Ethical Insufficiency Bridge Case
This provision requires engineers to know when the Code authorizes disclosure, making passive acquiescence to suppression a failure to apply this provision correctly.
-
BER Board Information Conveyance Mode Confidentiality Weight Differentiation Bridge Case
This provision's confidentiality protections vary by how information was obtained, requiring the Board capability to differentiate confidentiality weight by conveyance mode.
-
Engineer A Faithful Agent Client-Safety Balance Navigation Bridge Wall Defect
This provision defines the faithful agent confidentiality duty that must be balanced against Code-required public safety disclosure obligations.
-
Engineer A Sub-Consultant Independent Escalation Post-Suppression Bridge Wall
This provision authorizes independent escalation when the Code requires it, directly relating to whether Engineer A could escalate despite client suppression.
-
Engineer A Field Notes Wall Defect Non-Alteration
This provision requires truthfulness in professional reports and statements, directly supporting the obligation not to alter field notes documenting the wall defect.
-
Post-Verbal-Notification Written Confirmation Engineer A Wall Defect VWX
This provision requires objective and complete professional reporting, supporting the obligation to follow up verbal notification with written confirmation.
-
Engineering Notes Safety Finding Written Transmission Engineer A Wall Defect
This provision requires that all relevant information be included in professional reports, directly applying to the obligation to transmit the safety finding in writing.
-
Verbal-Only Disclosure Insufficiency Engineer A Wall Defect Public Agency
This provision requires complete and truthful professional reporting, supporting the obligation to recognize that verbal-only disclosure was insufficient.
-
Incidental Wall Defect Disclosure Engineer A VWX Bridge Inspection
This provision requires inclusion of all relevant and pertinent information in reports, directly applying to the obligation to disclose the incidentally observed defect.
-
Engineer A Speculative Wall Defect Formal Report Exclusion
This provision requires objectivity and truthfulness in reports, supporting the obligation to exclude speculative findings not confirmed by structural engineering analysis.
-
Engineer A Wall Defect Field Notes Documentation for Future Reference
This provision supports the obligation to document observations accurately for future reference as part of truthful professional record-keeping.
-
Confirmed-Fatality Mandatory Written Escalation Engineer A Wall Defect
This provision requires inclusion of all relevant and pertinent information, supporting the obligation to escalate in writing given the confirmed fatality context.
-
Document Out-of-Scope Defect in Field Notes
Recording the defect truthfully in field notes aligns with the duty to be objective and include all relevant information.
-
Comply with Instruction to Omit from Final Report
Omitting a known defect from the final report at the client's instruction violates the duty to include all relevant and pertinent information.
-
Retain Observation in Field Notes Only
Keeping the defect only in field notes and excluding it from the formal report may conflict with the duty to include all pertinent information in professional reports.
-
Engineer A Selective Omission in Final Bridge Inspection Report
This provision directly requires inclusion of all relevant and pertinent information in reports, making the omission of the wall defect finding a potential violation.
-
Client Chain Suppression of Wall Defect Finding
The provision is implicated when the client instructs Engineer A to exclude a potentially relevant safety finding from the final report.
-
Engineer A Verbal-Only Safety Report Without Written Documentation
The provision requires truthful and complete professional reports, raising questions about whether verbal-only reporting satisfies this obligation.
-
Engineer A Speculative Causal Link. Wall Defect to Accident
The provision requires objectivity and truthfulness, which bears on how Engineer A should characterize a speculative rather than confirmed causal finding in any report.
-
Post-Harm Speculative Causation. Structural Wall Failure Without Confirmed Defect
The provision governs how Engineer A must handle and report a speculative post-harm causal observation in professional statements or testimony.
-
Engineer A Scope-Exceeding Safety Discovery During Bridge Inspection
The provision's requirement to include all relevant and pertinent information applies even when the finding falls outside the contracted scope of work.
-
Written Report Completeness Wall Defect Omission Engineer A Bridge
II.3.a. requires inclusion of all relevant and pertinent information in professional reports, directly creating the obligation to include the wall defect observation.
-
Scope-of-Work Non-Exculpation Material Omission Engineer A Bridge Wall Report
II.3.a. prohibits omitting relevant information from reports regardless of scope limitations, making scope a non-excuse for the omission.
-
Client Suppression Instruction Non-Compliance Engineer A Wall Defect
II.3.a. requires truthful and complete reports, which is violated by complying with an instruction to omit a relevant observed defect.
-
Passive Acquiescence Suppression Instruction Engineer A Wall Defect Bridge
II.3.a. creates the completeness obligation that makes passive acquiescence to omitting the wall defect from the report a code violation.
-
Speculative Finding Written Report Exclusion. Engineer A Bridge Wall Defect
II.3.a. requires pertinent information in reports, and this constraint addresses whether a speculative finding qualifies as pertinent enough to require inclusion.
-
Competence Boundary Causal Surmise Epistemic Qualification Engineer A Bridge Wall
II.3.a. requires objective and truthful reporting, which is directly relevant to how Engineer A must qualify his causal surmise within the bounds of his competence.
-
Out-of-Scope Wall Defect Disclosure Engineer A Bridge
II.3.a. requires all relevant and pertinent information in reports, creating the disclosure obligation for the incidentally observed wall defect.
-
Verbal-Only Notification Written Follow-Up Engineer A Wall Defect VWX
II.3.a. requires complete written professional reporting, making verbal-only notification insufficient to satisfy the obligation to document relevant findings.
-
Verbal Disclosure Non-Substitution Written Public Authority Report Engineer A Bridge
II.3.a. requires written professional reports containing all relevant information, supporting the constraint that verbal disclosure does not substitute for written reporting.
-
Speculation-Grounded Observation Final Report Omission. Wall Defect Excluded from Pavement Report
II.3.a. requires truthful and complete professional reports, directly informing the Board's conclusion about what may properly be included or excluded based on evidentiary certainty.
-
Field Notes Integrity Preservation. Wall Defect Observation Must Not Be Altered
II.3.a. prohibits distorting facts in professional documents, directly supporting the requirement that field notes must not be altered even if the finding is excluded from the final report.
-
Factual Certainty vs. Speculation. Speculative Wall Defect Observation Calibrates Disclosure Obligation
II.3.a.'s requirement for truthful and pertinent reporting is the basis for calibrating disclosure obligations according to the speculative versus confirmed nature of the observation.
-
Client Report Suppression Prohibition Violated By Engineer A
II.3.a. requires inclusion of all relevant and pertinent information, making the client-directed suppression of the wall defect finding a violation of this provision.
-
Written Documentation Requirement Safety Notification Engineer A Engineering Notes
II.3.a. supports the obligation to document safety-relevant observations in professional reports, linking to the failure to translate field notes into a written notification.
-
Incidental Observation Disclosure Obligation Partially Satisfied By Engineer A
II.3.a. underpins the obligation to report all relevant observations, which Engineer A only partially satisfied through verbal disclosure.
-
Engineer A Bridge Sub-Consultant Inspector
Engineer A must be objective and truthful in reporting the observed structural defect, including all relevant information about its potential link to the fatal accident.
-
Engineer A Corrective Action Monitoring Sub-Consultant
Engineer A is obligated to provide truthful and complete professional statements regarding the out-of-scope defect observed during the inspection.
-
VWX Architects and Engineers Prime Consultant
VWX as prime consultant must ensure its professional reports and communications to the public agency are objective, truthful, and include all pertinent safety-related information.
-
Prime Consultant Bridge Project
The prime consultant bears responsibility for ensuring professional reports on the bridge project are complete and include all relevant findings including out-of-scope defects.
-
Pre-existing Defect Discovered
Discovering the defect creates an obligation to include all relevant and pertinent information in professional reports truthfully.
-
Information Confined to Field Notes
Keeping defect findings only in field notes rather than formal reports conflicts with the duty to include all relevant information in professional statements.
-
Suppression Instruction Issued
Being instructed to suppress the defect information directly conflicts with the requirement to be objective and truthful and include all pertinent information in reports.
-
Professional-Report-Integrity-Standard
This provision directly governs whether omitting the wall defect from the final report at client request violates the duty to include all relevant information.
-
Bridge-Inspection-Reporting-Standard
This provision requires completeness and accuracy in professional reports, directly applicable to the bridge inspection reporting obligations.
-
Out-of-Scope-Safety-Finding-Reporting-Standard-Individual
This provision establishes the truthfulness and completeness standard that informs whether Engineer A must report an out-of-scope safety finding.
-
NSPE-Code-Primary
This provision is part of the primary normative authority requiring Engineer A not to suppress relevant findings from professional reports.
-
Engineer A Engineering Notes Written Transmission Wall Defect
This provision requires objective and complete professional reports, directly requiring the capability to translate field notes into a formal written report including the wall defect.
-
Engineer A Verbal-to-Written Safety Notification Conversion Wall Defect
This provision requires that all relevant information appear in professional reports, requiring conversion of the verbal wall defect report into written documentation.
-
Engineer A Verbal-to-Written Finding Conversion Obligation Wall Defect
This provision establishes that professional reports must include all pertinent information, directly requiring recognition that verbal findings must be converted to written form.
-
Engineer A Scope-of-Work Non-Shield Safety Disclosure Bridge Wall Defect
This provision requires inclusion of all relevant and pertinent information in reports, meaning scope limitations do not excuse omission of safety-relevant observations.
-
Engineer A Passive Acquiescence Ethical Insufficiency Wall Defect
This provision requires truthful and complete reporting, making passive acquiescence to omit the wall defect from the final report a direct violation.
-
Engineer A Speculative Wall Defect Report Exclusion Bridge Case
This provision requires objectivity and truthfulness, requiring the capability to recognize that speculative causal surmises should be appropriately qualified rather than omitted entirely.
-
Engineer A Affirmative Public Safety Reporting Action Bridge Wall Defect
This provision requires complete and truthful professional reports, directly relating to the affirmative actions needed to fulfill reporting obligations for the wall defect.
-
Engineer A Incidental Wall Defect Identification Bridge Inspection
This provision requires inclusion of all relevant and pertinent information in reports, requiring that incidentally identified defects be reported when pertinent to safety.
-
Engineer A Incidental Out-of-Scope Wall Defect Identification Bridge Case
This provision requires complete professional reports including all pertinent information, directly applying to the obligation to report the incidentally observed wall defect.
-
Engineer A Domain-Specific Competence Boundary Wall Defect Bridge Case
This provision requires objective and truthful reporting, requiring the capability to accurately represent the limits of one's expertise when reporting the wall defect observation.
-
Engineer A Contextual Safety Reporting Calibration Bridge Fatality Wall Defect
This provision requires all relevant and pertinent information in reports, requiring calibration of reporting obligations to high-context factors like a confirmed fatality.
-
Engineer A Field Notes Wall Defect Preservation Non-Alteration Bridge Case
This provision requires truthful and complete professional reports, directly requiring preservation of field notes as the factual basis for accurate reporting.
-
Engineer A Field Notes Wall Defect Non-Alteration
This provision directly prohibits distorting or altering facts, which is the core of the obligation not to alter field notes documenting the wall defect.
-
Engineer A Speculative Wall Defect Formal Report Exclusion
This provision requires acknowledging errors and not distorting facts, supporting the obligation to exclude speculative findings that could misrepresent the engineering basis.
-
Client Report Suppression Resistance Engineer A Bridge Wall Defect
This provision prohibits distorting or altering facts, directly supporting the obligation to resist instructions to omit the wall defect finding from the final report.
-
Passive Acquiescence Suppression Instruction Engineer A Wall Defect
This provision prohibits distorting facts, directly applying to the obligation to actively resist suppression instructions that would effectively alter the factual record.
-
Comply with Instruction to Omit from Final Report
Omitting a known defect from the final report at the client's direction constitutes distorting or altering the facts.
-
Document Out-of-Scope Defect in Field Notes
Accurately documenting the defect reflects the duty to acknowledge errors and not distort facts.
-
Engineer A Selective Omission in Final Bridge Inspection Report
This provision prohibits distorting or altering facts, which is directly implicated by Engineer A omitting the wall defect finding from the final report at client direction.
-
Client Chain Suppression of Wall Defect Finding
The provision is relevant because complying with the client instruction to exclude the finding could constitute altering or distorting the factual record.
-
Engineer A Speculative Causal Link. Wall Defect to Accident
The provision requires acknowledging errors and not distorting facts, bearing on how Engineer A must accurately represent the speculative nature of the causal link.
-
Engineer A Verbal-Only Safety Report Without Written Documentation
The provision's requirement not to distort facts is relevant to whether verbal-only reporting without written documentation constitutes an incomplete or distorted record.
-
Post-Harm Speculative Causation. Structural Wall Failure Without Confirmed Defect
The provision requires Engineer A not to distort facts when characterizing the unconfirmed relationship between the observed defect and the fatal wall failure.
-
Field Notes Preservation Non-Alteration. Engineer A Bridge Wall Defect
III.1.a. prohibits distorting or altering facts, directly creating the obligation not to alter field notes documenting the wall defect.
-
Competence Boundary Causal Surmise Epistemic Qualification Engineer A Bridge Wall
III.1.a. requires acknowledging errors and not distorting facts, which constrains Engineer A to accurately represent his surmise as speculative rather than confirmed.
-
Passive Acquiescence Suppression Instruction Engineer A Wall Defect Bridge
III.1.a. prohibits distorting or altering facts, making passive acquiescence to suppressing a factual observation a violation of this provision.
-
Engineering Notes Written Transmission Wall Defect Engineer A Bridge
III.1.a. requires not distorting facts, supporting the obligation to transmit documented observations rather than allowing them to remain suppressed in personal notes.
-
Speculative Observation Verbal-Only Subconsultant Escalation. Engineer A to VWX
III.1.a. requires honest acknowledgment of the nature of findings, supporting the constraint that Engineer A accurately characterize the observation as speculative when escalating.
-
Field Notes Integrity Preservation. Wall Defect Observation Must Not Be Altered
III.1.a. directly prohibits distorting or altering facts, which is the exact obligation the Board invokes to protect the integrity of Engineer A's field notes.
-
Client Report Suppression Prohibition Violated By Engineer A
III.1.a. requires engineers not to distort or alter facts, making compliance with the suppression instruction a direct violation of this provision.
-
Passive Acquiescence After Safety Notification Independent Ethical Failure Engineer A
III.1.a. obligates engineers to acknowledge errors and not alter facts, meaning passive acquiescence to suppression constitutes an independent failure under this provision.
-
Speculation-Grounded Observation Final Report Omission. Wall Defect Excluded from Pavement Report
III.1.a. informs the distinction between legitimately omitting speculative findings from a report versus improperly altering or suppressing documented facts.
-
Engineer A Bridge Sub-Consultant Inspector
Engineer A must acknowledge the observed defect honestly and not distort or minimize the facts regarding the potential structural failure linked to the fatal accident.
-
VWX Architects and Engineers Prime Consultant
VWX must not distort or alter the facts communicated by Engineer A regarding the structural defect when reporting to the public agency.
-
Engineer A Corrective Action Monitoring Sub-Consultant
Engineer A must acknowledge findings accurately and not alter facts about the observed defect when communicating with VWX or other parties.
-
Suppression Instruction Issued
Following the suppression instruction would constitute distorting or altering the facts, which engineers are prohibited from doing.
-
Information Confined to Field Notes
Concealing discovered defect data by limiting it to field notes amounts to distorting the factual record of the inspection.
-
Officer B Fatal Crash
The fatal crash outcome underscores the consequence of not acknowledging known errors or defects, linking the harm to the failure to disclose facts.
-
Professional-Report-Integrity-Standard
This provision directly prohibits distorting or altering facts, which applies to omitting the wall defect finding from the report at client request.
-
Bridge-Inspection-Reporting-Standard
This provision requires engineers to acknowledge errors and not distort facts, directly relevant to completeness obligations in bridge inspection reporting.
-
NSPE-Code-Primary
This provision is part of the primary normative authority prohibiting Engineer A from suppressing or distorting observed safety findings.
-
Engineer A Field Notes Wall Defect Preservation Non-Alteration Bridge Case
This provision requires engineers not to distort or alter facts, directly requiring the capability to preserve field notes documenting the wall defect without alteration.
-
Engineer A Passive Acquiescence Ethical Insufficiency Wall Defect
This provision requires acknowledgment of errors and prohibits distortion of facts, making passive acquiescence to omit a documented observation a violation of this duty.
-
Engineer A Client Suppression Instruction Recognition Wall Defect
This provision prohibits distorting or altering facts, requiring recognition that complying with a suppression instruction constitutes impermissible alteration of the factual record.
-
Engineer A Engineering Notes Written Transmission Wall Defect
This provision prohibits distortion of facts, requiring that engineering notes documenting the wall defect be faithfully transmitted rather than suppressed or altered.
-
Engineer A Speculative Wall Defect Report Exclusion Bridge Case
This provision requires not distorting facts, requiring the capability to accurately characterize speculative observations as speculative rather than omitting them entirely.
-
Engineer A Passive Acquiescence Suppression Instruction Ethical Insufficiency Bridge Case
This provision prohibits distorting or altering facts, making passive acquiescence to a suppression instruction a direct failure to uphold this obligation.
-
BER Board Confirmed-Fatality vs Future-Risk Escalation Threshold Differentiation Bridge Case
This provision requires acknowledgment of factual distinctions, requiring the Board capability to accurately distinguish confirmed fatality facts from speculative future risk facts.
-
Engineer A Present-vs-Precedent Factual Distinction Bridge Wall vs Case 89-7
This provision requires not distorting facts, requiring the capability to accurately distinguish the present case facts from precedent rather than misapplying prior rulings.
-
Client Report Suppression Resistance Engineer A Bridge Wall Defect
This provision requires notifying proper authorities and withdrawing if a client insists on unprofessional conduct, directly supporting the obligation to resist the suppression instruction.
-
Passive Acquiescence Suppression Instruction Engineer A Wall Defect
This provision requires engineers to notify proper authorities rather than passively acquiesce when clients insist on omitting required safety information.
-
Sub-Consultant Independent Escalation Engineer A Post-Suppression Bridge Wall
This provision supports the obligation to independently escalate to proper authorities after receiving a suppression instruction through the client chain.
-
Confirmed-Fatality Mandatory Written Escalation Engineer A Wall Defect
This provision requires notification of proper authorities when clients insist on unprofessional conduct, directly applying to the confirmed-fatality escalation obligation.
-
Contextually Calibrated Escalation Engineer A Bridge Fatality Wall Defect
This provision requires notifying proper authorities in cases of unprofessional client conduct, supporting the obligation to calibrate escalation to the high-context factors present.
-
Engineer A Case 89-7 Confidentiality Agreement Building Code Violation Reporting
This provision directly governed the obligation in Case 89-7 to report confirmed code violations to appropriate authorities notwithstanding client objections.
-
Corrective Action Monitoring Engineer A Bridge Wall Defect Post-Verbal-Report
This provision implies an ongoing duty to ensure proper authorities are notified if corrective action is not taken, supporting the post-verbal-report monitoring obligation.
-
Engineer A Corrective Action Follow-Through Monitoring Bridge Wall Defect
This provision supports the obligation to follow through to ensure corrective action occurs, as it requires engineers to notify proper authorities when safety standards are not met.
-
Comply with Instruction to Omit from Final Report
If omitting the defect results in a report that does not conform to engineering standards, the engineer must refuse and notify proper authorities.
-
Decline to Report to External Authorities
This provision requires notifying proper authorities when a client insists on unprofessional conduct, making declining to report potentially non-compliant.
-
Client Chain Suppression of Wall Defect Finding
This provision directly addresses the situation where a client insists on conduct that compromises professional standards, requiring notification of proper authorities and withdrawal.
-
Engineer A No External Escalation After Suppression
The provision is directly implicated by Engineer A's failure to notify proper authorities after both VWX and the public agency suppressed the safety finding.
-
Engineer A Selective Omission in Final Bridge Inspection Report
The provision applies because signing or sealing a report that omits safety-relevant information at client insistence may constitute unprofessional conduct requiring escalation.
-
Public Safety at Risk. Bridge Wall Structural Integrity
The provision's requirement to notify proper authorities is directly relevant to the ongoing unaddressed public safety risk from the defective bridge wall condition.
-
Engineer A's Obligation to Monitor Public Agency Follow-Through
The provision implies a continuing duty to ensure proper authorities are informed if the client fails to act, supporting Engineer A's obligation to monitor follow-through.
-
Graduated Escalation. Speculative Concern Requiring Calibrated Response
The provision's requirement to notify proper authorities must be calibrated to the speculative nature of the concern, informing the appropriate level of escalation.
-
Client-Loyalty vs. Public Safety Paramount Obligation Conflict
The provision resolves the conflict by prioritizing notification of proper authorities over client loyalty when unprofessional conduct is insisted upon.
-
Client Suppression Instruction Non-Compliance Engineer A Wall Defect
III.2.b. requires engineers to notify proper authorities and withdraw when clients insist on unprofessional conduct, directly creating the non-compliance obligation when VWX relayed the suppression instruction.
-
Subconsultant Independent Escalation Post-Suppression Engineer A Bridge Wall
III.2.b. requires notifying proper authorities when a client insists on unprofessional conduct, creating the independent escalation obligation after the suppression instruction was received.
-
Post-Client-Override Regulatory Escalation Engineer A Bridge Wall Defect
III.2.b. requires notifying proper authorities when the client overrides professional judgment, directly creating the regulatory escalation obligation after the public agency suppressed the finding.
-
Persistent Escalation Beyond Unresponsive Public Agency Engineer A Bridge Wall
III.2.b. requires notifying proper authorities when clients insist on unprofessional conduct, supporting the obligation to escalate beyond an unresponsive public agency.
-
Public Safety Paramount Client Suppression Engineer A Bridge Wall
III.2.b. establishes the duty to notify authorities and withdraw when clients insist on unprofessional conduct, directly supporting the public safety paramount constraint over client suppression.
-
Client Loyalty Public Safety Priority Engineer A Bridge Wall Defect
III.2.b. resolves the conflict between client loyalty and public safety by requiring notification of proper authorities when clients insist on unprofessional conduct.
-
Scope Non-Shield Wall Defect Engineer A Bridge Inspection
III.2.b. imposes obligations regardless of contracted scope when professional standards are at issue, supporting the constraint that scope does not shield Engineer A from disclosure obligations.
-
Public Infrastructure Fatal Accident Scope Non-Shield Engineer A Bridge Wall
III.2.b. requires notifying proper authorities when professional standards are violated, reinforcing that public infrastructure and a confirmed fatality remove any scope-based shield.
-
Client Report Suppression Prohibition Violated By Engineer A
III.2.b. directly addresses the situation where a client insists on unprofessional conduct, requiring notification of proper authorities and withdrawal, which maps onto the suppression instruction.
-
Multi-Authority Escalation Obligation Violated By Engineer A Post-Suppression
III.2.b. requires notifying proper authorities when a client insists on unprofessional conduct, directly grounding the escalation obligation after the suppression instruction was issued.
-
Post-Client-Refusal Escalation Assessment Obligation Violated By Engineer A
III.2.b. establishes the duty to escalate to proper authorities after client refusal to act appropriately, which Engineer A failed to assess and execute.
-
Post-Client-Refusal Escalation Assessment. Conditional External Reporting If No Corrective Action
III.2.b. is the code basis for the Board's conditional external reporting obligation if the public agency takes no corrective action after notification.
-
Sub-Consultant Safety Escalation Independence Obligation Violated By Engineer A
III.2.b. supports the principle that even a sub-consultant must independently notify proper authorities when the client insists on suppressing safety-relevant findings.
-
Corrective Action Monitoring Before External Escalation. Engineer A Must Follow Through
III.2.b. underlies the ongoing obligation to follow through and notify proper authorities if the client does not take corrective action.
-
Premature External Escalation Reputational Harm. Reporting Before Corrective Action Determination Would Be Overreaction
III.2.b. implicitly requires that the client first insist on unprofessional conduct before external escalation is triggered, supporting the Board's sequencing of corrective action assessment before external reporting.
-
Engineer A Bridge Sub-Consultant Inspector
If instructed to ignore or not report the structural defect that violates engineering standards, Engineer A must notify proper authorities and consider withdrawing from the project.
-
VWX Architects and Engineers Prime Consultant
VWX must not complete or seal plans that fail to address known structural deficiencies, and must notify proper authorities if the public agency insists on proceeding without remediation.
-
Prime Consultant Bridge Project
The prime consultant is responsible for ensuring plans conform to applicable engineering standards and must act if the client insists on proceeding despite known structural defects.
-
Bridge Inspection Initiated
The inspection process is the professional service context in which signing off on a deficient structure without reporting nonconformities would violate this provision.
-
Pre-existing Defect Discovered
Discovering a defect that renders the bridge non-conformant with engineering standards triggers the duty to notify proper authorities rather than conceal it.
-
Suppression Instruction Issued
The employer instructing suppression of defect information is precisely the unprofessional conduct scenario where the engineer must notify proper authorities and consider withdrawal.
-
Engineer-Public-Safety-Escalation-Standard
This provision requires notifying proper authorities when a client insists on unprofessional conduct, directly governing Engineer A's escalation obligation.
-
Engineer_Public_Safety_Escalation_Standard_Instance
This provision establishes the duty to follow through with proper authorities if the client suppresses safety findings, which this entity operationalizes.
-
Engineer-Safety-Recommendation-Rejection-Standard
This provision governs Engineer A's obligations after the client effectively rejects his safety finding by instructing him not to include it in the report.
-
Client-Confidentiality-vs-Public-Safety-Balancing-Framework
This provision informs the balancing framework by establishing that client insistence on unprofessional conduct triggers a duty to notify authorities.
-
NSPE-Code-Primary
This provision is part of the primary normative authority requiring Engineer A to notify proper authorities rather than comply with client suppression instructions.
-
Engineer A Sub-Consultant Independent Escalation Post-Suppression Bridge Wall
This provision requires notifying proper authorities and withdrawing when a client insists on unprofessional conduct, directly requiring independent escalation capability after suppression.
-
Engineer A Client Suppression Instruction Recognition Wall Defect
This provision requires recognizing when a client instruction constitutes insistence on unprofessional conduct requiring notification of proper authorities.
-
Engineer A Passive Acquiescence Ethical Insufficiency Wall Defect
This provision requires affirmative action when clients insist on unprofessional conduct, making passive acquiescence to suppression a direct failure of this obligation.
-
Engineer A Affirmative Public Safety Reporting Action Bridge Wall Defect
This provision requires notification of proper authorities when clients insist on unprofessional conduct, directly requiring determination of affirmative reporting actions.
-
Engineer A Multi-Agency Jurisdiction Identification Bridge Wall Escalation
This provision requires notifying proper authorities, directly requiring the capability to identify all agencies and authorities having jurisdiction over the bridge wall safety concern.
-
Engineer A Confidentiality Pre-emption Public Safety Bridge Wall
This provision requires escalation to proper authorities over client objection, directly requiring recognition that public safety pre-empts confidentiality in this context.
-
Engineer A Corrective Action Monitoring Post-Verbal-Report Bridge Wall
This provision implies a continuing obligation to ensure proper authorities are notified, requiring monitoring of whether corrective action was taken after the verbal report.
-
Engineer A Corrective Action Monitoring Bridge Wall Defect Post-Verbal-Report
This provision requires ensuring proper authorities are engaged when unprofessional conduct is insisted upon, requiring follow-through monitoring of corrective action.
-
Engineer A Public Infrastructure Fatality Heightened Escalation Threshold Bridge Wall
This provision requires notification of proper authorities in cases of unprofessional conduct, requiring recognition that public infrastructure and confirmed fatality heighten this escalation threshold.
-
VWX Prime Consultant Sub-Consultant Safety Escalation Sequencing Bridge Wall
This provision requires proper authority notification when unprofessional conduct is insisted upon, requiring VWX to correctly sequence safety escalation obligations as prime consultant.
-
Engineer A Passive Acquiescence Suppression Instruction Ethical Insufficiency Bridge Case
This provision requires affirmative notification of proper authorities rather than passive acquiescence when a client insists on omitting safety-relevant information.
-
Engineer A Scope-of-Work Non-Shield Recognition Bridge Wall
This provision applies regardless of contracted scope, requiring recognition that scope limitations do not shield an engineer from the obligation to notify proper authorities.
Cross-Case Connections
View ExtractionExplicit Board-Cited Precedents 1 Lineage Graph
Cases explicitly cited by the Board in this opinion. These represent direct expert judgment about intertextual relevance.
Principle Established:
When an engineer becomes aware of safety violations that could injure the public, the obligation to hold paramount public health and safety overrides the duty of confidentiality to the client, and the engineer must report the violations to appropriate public authorities.
Citation Context:
The Board cited this case as the primary precedent for analyzing the conflict between an engineer's duty of confidentiality to a client and the obligation to protect public health and safety. It is both analogized and distinguished from the present case.
Principle Established:
The principles from Case No. 89-7 regarding the conflict between engineer confidentiality obligations and public safety obligations have been applied in subsequent BER decisions.
Citation Context:
The Board cited this case to show that the principles established in Case No. 89-7 had been previously applied in another BER decision, reinforcing the precedential weight of those principles.
Implicit Similar Cases 10 Similarity Network
Cases sharing ontology classes or structural similarity. These connections arise from constrained extraction against a shared vocabulary.
Questions & Conclusions (2 board)
View ExtractionWas it ethical for Engineer A to retain the information in his engineering notes but not include it in the final report as requested?
Implicit (4)
Given that a person died in an accident potentially linked to the defective wall condition, does the confirmed fatality independently trigger a mandatory written escalation obligation that overrides the Board's conditional 'corrective action' tolerance, regardless of whether the public agency has been verbally informed?
Is a verbal report through a client chain - from Engineer A to VWX to the public agency - a legally and ethically sufficient form of safety notification when the subject matter involves a potential contributing cause to a fatality on public infrastructure, or does the mode of transmission itself constitute an independent ethical failure?
What specific corrective action, within what timeframe, and verified by what mechanism, must the public agency take before Engineer A's continued silence becomes an independent ethical violation - and who bears responsibility for defining and monitoring that threshold?
Does Engineer A's status as a subconsultant - rather than the prime consultant - reduce, eliminate, or merely sequence his independent public safety escalation obligation, and does the Board's deference to the prime consultant's 'superior contextual knowledge' inappropriately insulate Engineer A from direct accountability to the public?
Was it ethical for Engineer A not to report this information to any other public agency or authority?
Principle tension (4)
Does the principle of Epistemic Humility - that Engineer A should calibrate his response to his speculative, non-structural-engineer observation - conflict with the Confirmed-Fatality Escalation Trigger principle, which holds that a known death linked to the defect demands heightened mandatory action regardless of the observer's domain expertise?
Does the Faithful Agent Obligation - requiring Engineer A to act as a loyal agent and trustee of his client - fundamentally conflict with the Client Report Suppression Prohibition, and if so, does the Board's conclusion that omitting the finding from the final report was ethical improperly subordinate public safety paramountcy to client loyalty in a context involving a confirmed fatality?
Does the Scope-Bounded Public Safety Obligation principle - which holds that Engineer A's duties are limited to his contracted pavement inspection scope - conflict with the Out-of-Scope Safety Observation Discretionary Response principle and the Public Welfare Paramount principle, and does allowing scope-of-work to modulate safety reporting obligations create a dangerous precedent for engineers who incidentally discover life-safety hazards?
Does the Premature External Escalation Reputational Harm principle - cautioning against reporting before corrective action is assessed - conflict with the Multi-Authority Escalation Obligation principle and the Post-Client-Refusal Escalation Assessment obligation, and does the Board's tolerance of Engineer A's silence improperly weight reputational and client-relationship concerns over the public's right to know about a potentially dangerous bridge wall?
Cross-cutting analytical questions (8)
These questions consider the case as a whole rather than a specific board question above.
Show 8 cross-cutting questionsTheoretical (4)
From a deontological perspective, did Engineer A fulfill their categorical duty to protect public safety by merely making a verbal report and then acquiescing to the suppression instruction, given that a person had already died and a structural defect potentially linked to that death remained undocumented in any official record?
From a consequentialist perspective, did the Board's conditional approval - that non-escalation is ethical only if corrective action is taken within a relatively short period - adequately account for the risk that no enforcement mechanism exists to ensure the public agency actually follows through, leaving the public exposed to an ongoing structural hazard?
From a virtue ethics perspective, did Engineer A demonstrate the professional integrity and courage expected of a licensed engineer by accepting the suppression instruction without producing a written record of the safety concern, or did this passive acquiescence represent a failure of the virtues of honesty, fortitude, and professional responsibility?
From a deontological perspective, does Engineer A's status as a subconsultant - rather than a prime consultant - diminish or eliminate the independent duty owed directly to the public, or does the NSPE Code impose that duty on every licensed engineer regardless of contractual position in the project hierarchy?
Counterfactual (4)
If Engineer A had converted the verbal safety report into a written memorandum transmitted directly to both VWX and the public agency before the suppression instruction was issued, would the public agency have been legally and ethically unable to request omission of the finding, and would the outcome for public safety have been materially different?
If the wall defect had been within Engineer A's explicit scope of work rather than incidentally discovered, would the Board have reached the same conclusion permitting omission from the final report, or would the scope inclusion have created an unambiguous obligation to document and report the finding regardless of client instruction?
If Engineer A had reported the wall defect finding directly to a relevant regulatory or safety authority immediately after receiving the suppression instruction, rather than waiting to monitor whether the public agency took corrective action, would the Board have considered that escalation premature and professionally harmful, or would the confirmed fatality context have justified immediate independent reporting?
If the facts of this case had been identical to NSPE Case No. 89-7 - where the engineer received information through a confidential client relationship rather than through independent field observation - would Engineer A's obligation to report to external authorities have been stronger, weaker, or equivalent, and what does that comparison reveal about whether the Board's source-of-information distinction is ethically principled or merely pragmatic?
Decisions & Arguments (6)
View ExtractionShould Engineer A retain the wall defect observation solely in private field notes, produce a written memorandum to VWX documenting the observation and his surmise, or include the finding in the final report despite the client's suppression instruction?
The Speculation-Grounded Observation Final Report Omission Permissibility Principle supports retaining the finding in field notes only, given that the observation was speculative and outside Engineer A's structural competence. The Field Notes Integrity and Alteration Prohibition Principle requires that field notes be preserved as an authentic evidentiary record. The Confirmed-Fatality-Linked Incidental Observation Mandatory Written Escalation Obligation demands that the confirmed-fatality context elevates the observation to require written documentation transmitted to responsible parties, not merely private retention. The Written Documentation Requirement Safety Notification principle further supports producing a written memorandum to VWX as a minimum floor independent of the final report.
Uncertainty arises because the suppression instruction addressed the final report specifically, and Engineer A could reasonably interpret it as not prohibiting an internal written memorandum to VWX. However, the Board's conclusion that field-notes-only retention was ethical is contested by the confirmed-fatality context, which raises the evidentiary stakes to a level where private notes inaccessible to any public authority are structurally insufficient. The speculative nature of the causal surmise moderates but does not eliminate the written documentation obligation.
Engineer A, a civil engineer retained as subconsultant for pavement inspection, incidentally observed a pre-existing wall defect and professionally surmised it may have causally contributed to Police Officer B's confirmed fatal crash. VWX relayed the public agency's instruction to omit the finding from the final report. Engineer A verbally reported the observation through the client chain but produced no written artifact beyond private field notes.
Should Engineer A resist VWX's instruction to omit the wall defect finding from the final report, comply with the instruction while retaining the observation in field notes, or comply with the instruction while producing a separate written notification to the public agency documenting the suppression?
The Client Report Suppression Resistance obligation holds that Engineer A was obligated to resist VWX's instruction, recognizing that the public agency's direction did not extinguish his obligation to ensure public authorities had accurate safety information. The Faithful Agent Obligation supports compliance with the client's instruction as a legitimate exercise of client loyalty within the bounds of professional ethics. The Speculation-Grounded Observation Final Report Omission Permissibility Principle supports compliance on the grounds that speculative, unverified findings may permissibly be omitted from formal reports when preserved in field notes and verbally communicated. The Confirmed-Fatality Escalation Trigger Principle holds that the death of Police Officer B materially heightens Engineer A's obligation beyond what the ordinary out-of-scope discretionary response standard would require.
The Faithful Agent Obligation's force as a rebuttal to the suppression prohibition is weakened when the suppressed finding is causally linked, even speculatively, to a confirmed fatality. The speculative nature of Engineer A's causal surmise moderates the suppression prohibition but does not eliminate it, because the observation's potential relevance to a death is itself the trigger for disclosure regardless of causal certainty. The absence of a confidentiality agreement reduces the confidentiality rationale for compliance.
VWX relayed the public agency's instruction asking Engineer A not to include the wall defect finding in his final report because it was not part of his scope of work. Engineer A stated he would retain the information in his engineering notes but not include it in the final report as requested. A confirmed fatality, Police Officer B, had occurred in circumstances potentially linked to the defect Engineer A observed.
Should Engineer A report the wall defect finding independently to an external public authority immediately after receiving the suppression instruction, defer independent reporting pending a defined monitoring period for corrective action, or refrain from independent external reporting entirely given his subconsultant status and the speculative nature of his observation?
The Sub-Consultant Suppression-Instruction Independent Escalation Obligation holds that the subconsultant relationship does not extinguish Engineer A's independent professional obligation to escalate to appropriate public authorities when the client chain issues a suppression instruction. The Premature External Escalation Reputational Harm Avoidance Principle cautions against escalating before determining whether the internal chain has taken corrective action, to avoid unjustifiably damaging professional reputations. The Prime Consultant Contextual Superiority Deference Principle supports deferring to VWX's superior contextual knowledge before independently escalating. The Confirmed-Fatality Escalation Trigger Principle holds that the confirmed death of Police Officer B materially heightens Engineer A's obligation beyond the ordinary corrective-action-monitoring tolerance. The Corrective Action Monitoring obligation requires Engineer A to affirmatively seek confirmation of corrective action rather than passively waiting.
The Premature External Escalation warrant loses force once the client chain has affirmatively suppressed the finding rather than acting on it, and once the public agency, the entity responsible for corrective action, is itself the source of the suppression instruction. The subconsultant deference warrant is exhausted once the prime consultant has transmitted rather than resisted the suppression instruction, activating rather than suspending Engineer A's independent escalation obligation. The speculative nature of the causal surmise moderates but does not eliminate the escalation obligation when a fatality has already occurred.
Engineer A verbally reported the wall defect to VWX, which relayed it to the public agency. The public agency issued a suppression instruction through VWX. Engineer A complied and did not report to any other public agency or authority. Police Officer B had died in a crash potentially linked to the defect. The public agency, the entity responsible for the bridge, was the same entity that issued the suppression instruction, making it structurally incapable of serving as a neutral corrective-action monitor.
Should Engineer A treat his subconsultant status as sequencing his escalation obligation, deferring to VWX's superior contextual knowledge even after the suppression instruction, or as activating his independent escalation duty once VWX transmitted rather than resisted the suppression instruction?
The Prime Consultant Contextual Superiority Deference Principle supports continued deference to VWX even after the suppression instruction, on the grounds that VWX possesses superior knowledge of the project's history, prior work, and stakeholder dynamics that may justify the suppression decision. The Sub-Consultant Safety Escalation Independence Obligation holds that the subconsultant relationship does not extinguish Engineer A's independent professional obligation and that the prime consultant's role as communication intermediary does not transfer Engineer A's ethical responsibility to VWX. The Conduit Forfeiture Rule holds that when a prime consultant transmits rather than resists a suppression instruction, it forfeits its claim to contextual superiority and activates rather than suspends the subconsultant's independent escalation obligation.
The deference warrant retains some force if VWX's transmission of the suppression instruction reflected a genuine professional judgment, informed by superior contextual knowledge, that the verbal report to the public agency was sufficient and that the agency would take corrective action. However, this assumption is structurally undermined when the public agency is itself the source of the suppression instruction, making it unreasonable to rely on that agency's self-reporting of corrective action as the trigger for Engineer A's escalation. The absence of any confidentiality agreement further reduces the basis for continued deference.
Engineer A was retained by VWX as a subconsultant for pavement inspection. He verbally reported the wall defect to VWX, which relayed it to the public agency. The public agency issued a suppression instruction, which VWX transmitted to Engineer A rather than resisting it. Engineer A complied and did not escalate independently. The NSPE Code imposes the public safety paramount duty on every licensed engineer by virtue of licensure, not contractual position.
Should Engineer A calibrate his reporting obligation downward based on the speculative, out-of-scope nature of his wall defect observation, or calibrate it upward based on the confirmed fatality context, and does that calibration determine whether a verbal client-chain report is sufficient or whether written escalation to public authorities is mandatory?
The Epistemic Humility Constraint holds that Engineer A should calibrate his response to his speculative, non-structural-engineer observation, justifying a verbal report with appropriate qualification rather than a formal written finding. The Confirmed-Fatality Escalation Trigger Principle holds that a known death plausibly linked to the defect demands heightened mandatory action regardless of domain expertise, because the observation's potential relevance to a death is itself the trigger for disclosure. The Contextually Calibrated Escalation obligation requires Engineer A to calibrate his reporting to the high-context factors present: confirmed fatality, structural defect on public infrastructure, professional surmise of causal connection, public bridge with ongoing traffic, which collectively required escalation beyond a verbal client-chain report.
The Confirmed-Fatality Escalation Trigger loses some force if the causal link between the pre-existing defect and the fatal accident remains genuinely speculative rather than confirmed, because the trigger's mandatory character depends on the plausibility of the causal connection. However, the Board's framework conflates the standard of certainty required for a causal conclusion with the standard of concern required for a safety notification: these are distinct thresholds, and the latter is appropriately low and triggered by reasonable suspicion rather than confirmed causation. Epistemic humility should calibrate the engineer's own causal conclusions, not the intensity of the escalation pathway used to bring the concern to qualified attention.
Engineer A, a civil engineer specializing in pavement inspection rather than structural engineering, observed a pre-existing wall defect and professionally surmised, without confirmatory testing or structural expertise, that it may have causally contributed to Police Officer B's confirmed fatal crash. He verbally reported this observation through the client chain. The confirmed fatality is the critical contextual variable that the Board acknowledged but did not treat as an independent escalation trigger.
Should Engineer A treat his pavement-only scope of work as justifying discretionary, verbal-only disclosure of the incidentally observed wall defect, or as defining only his analytical investigation duty, leaving intact a non-scope-conditional written documentation obligation to ensure the safety concern is accessible to responsible public authorities?
The Scope-Bounded Public Safety Obligation Principle supports treating the pavement-only scope as reducing Engineer A's wall defect reporting obligation to discretionary, since he was not retained to assess structural conditions and his observation was incidental. The Public Welfare Paramount principle holds that the obligation to protect public safety overrides scope-of-work boundaries when a life-safety hazard is incidentally discovered, because every licensed engineer retains independent Code obligations regardless of contractual scope. The Scope-of-Work Limitation as Incomplete Ethical Defense principle holds that scope of work defines the engineer's affirmative deliverable obligations to the client, not a ceiling on the engineer's independent safety disclosure obligations to the public.
The scope-limitation warrant's force as a rebuttal to the public welfare paramount obligation is undermined when the out-of-scope hazard has already materialized in a confirmed fatality, because the prospective-risk rationale for scope-based discretion does not apply when harm has already occurred. The Board's reasoning, if generalized, would mean that an engineer contracted to inspect one system who incidentally observes a life-threatening hazard in another system may ethically omit that observation from any written record simply because it was out of scope, an outcome irreconcilable with the Code's public safety paramount requirement.
Engineer A's scope of work was solely to identify pavement damage on the bridge and report it to VWX. The wall defect was incidentally observed outside that scope. The Board used the out-of-scope nature of the observation as a mitigating factor reducing Engineer A's reporting obligation. A confirmed fatality, Police Officer B, had occurred in circumstances potentially linked to the defect. The NSPE Code's public welfare paramount obligation is not conditioned on whether the hazard falls within the engineer's contracted deliverables.
Event Timeline (12)
Case timeline
- Potential failure to anticipate and address how out-of-scope safety observations by subconsultant would be handled
- Obligation to structure subconsultant agreements in ways that do not inadvertently suppress public safety reporting
- Contractual duty to define scope of services clearly
- Professional obligation to engage competent specialists for specific tasks
- Professional obligation to maintain accurate and complete engineering field notes
- Obligation not to alter or suppress professional observations made during the course of work
- Duty to preserve information that may bear on public health and safety
- Obligation to hold paramount public health and safety by surfacing potentially relevant hazard information
- Duty of candor and transparency with client regarding professionally observed conditions
- Obligation to bring safety-relevant information to the attention of those with authority and expertise to act
- Arguably, failure to follow up verbal report in writing reduced the enforceability and traceability of the disclosure
- Arguably, omission from the formal record weakens the enforceability of the safety concern and reduces accountability for follow-up action
- Ongoing obligation to ensure corrective action is taken was not yet discharged at this point
- Fidelity to client instructions within reasonable professional bounds
- Professional responsibility to limit formal report content to areas of competence and verified findings
- Obligation not to include speculative, unverified conclusions in a formal engineering report
- Professional obligation to maintain accurate and unaltered engineering field notes
- Integrity in professional documentation, not destroying or altering records of professional observations
- Preservation of information that may be relevant to public safety and legal accountability
- Ongoing obligation to follow through and ensure corrective action is actually taken, not yet discharged
- Arguably, paramount duty to public health and safety may require independent reporting if client chain fails to act
- Obligation to consider alternatives if public agency does not take corrective action (per Discussion)
- Reasonable deference to the prime consultant and public agency who have broader project authority and context
- Avoidance of premature escalation based on unverified, speculative observations
- Fidelity to client relationship within ethical limits
Narrative (3 main characters)
View ExtractionOpening 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 civil engineer retained by VWX Architects and Engineers as a subconsultant to inspect pavement damage on a bridge undergoing a major scheduled overhaul for a public agency. Your contracted scope covers pavement conditions only. During your inspection, you notice an apparent pre-existing defective condition in a bridge wall near the location where, three months earlier, a patrol car driven by Police Officer B crashed through the wall and fell into the river below, killing him. You reported this observation verbally to VWX, which passed it verbally to the public agency, but VWX has since instructed you to omit the wall defect finding from your final report on the grounds that it falls outside your scope of work. You must now work through a series of decisions about how to document, report, and respond to that instruction.
Main characters (3)
Each card shows the roles a person holds and the tensions those roles raise for them. A single person may carry several roles in the case, and a tension between obligations can implicate more than one person at once. Click Show all tensions for the full list.
Engineer A has a confirmed obligation to produce written escalation when a fatality is linked to an incidentally observed defect, yet the constraint prohibiting speculative findings from written reports creates a direct conflict: if the causal link between the wall defect and the officer's death cannot be established with engineering certainty, the exclusion constraint may be invoked to suppress the very written report the fatality-linked escalation obligation demands. The dilemma is genuine because acting on the obligation risks violating epistemic standards, while honoring the constraint risks suppressing safety-critical information in a confirmed-fatality context.
Engineer A has a confirmed obligation to produce written escalation when a fatality is linked to an incidentally observed defect, yet the constraint prohibiting speculative findings from written reports creates a direct conflict: if the causal link between the wall defect and the officer's death cannot be established with engineering certainty, the exclusion constraint may be invoked to suppress the very written report the fatality-linked escalation obligation demands. The dilemma is genuine because acting on the obligation risks violating epistemic standards, while honoring the constraint risks suppressing safety-critical information in a confirmed-fatality context.
Tension between Confirmed-Fatality Mandatory Written Escalation Engineer A Wall Defect and Speculative Observation Verbal-Only Subconsultant Escalation Permissibility Constraint
When the prime consultant instructs Engineer A (as sub-consultant) to suppress the wall defect finding, Engineer A's obligation to escalate independently conflicts with the constraint that the prime consultant may possess superior contextual knowledge warranting deference. The tension is genuine because deference to the prime's judgment is professionally reasonable in normal circumstances, yet the suppression instruction in a confirmed-fatality context transforms that deference into complicity. Honoring the deference constraint risks passive acquiescence to suppression; overriding it risks breaching the hierarchical professional relationship and potentially acting on incomplete contextual understanding.
Engineer A is obligated to follow up verbal notification of the wall defect with written confirmation, yet the client has issued a suppression instruction that the constraint framework recognizes must not be complied with. These two elements together create a layered dilemma: the written confirmation obligation is the correct professional response to verbal-only disclosure insufficiency, but producing that written confirmation directly defies the client's explicit suppression instruction. The engineer cannot simultaneously satisfy the client relationship and fulfill the written escalation duty, making this a genuine obligation-versus-constraint conflict where professional ethics override client authority.
Potential tension between Confidentiality Non-Override Public Danger Engineer A Bridge Wall Defect and Engineer A Faithful Agent Client Loyalty Balance Bridge Wall Defect
Potential tension between Verbal-Only Disclosure Insufficiency Engineer A Wall Defect Public Agency and Engineer A Faithful Agent Client Loyalty Balance Bridge Wall Defect
Tension between Engineer A Wall Defect Field Notes Documentation for Future Reference and Speculative Observation Verbal-Only Subconsultant Escalation Permissibility Constraint
Other people involved in the case but not central to the opening narrative.
Engineer A has a confirmed obligation to produce written escalation when a fatality is linked to an incidentally observed defect, yet the constraint prohibiting speculative findings from written reports creates a direct conflict: if the causal link between the wall defect and the officer's death cannot be established with engineering certainty, the exclusion constraint may be invoked to suppress the very written report the fatality-linked escalation obligation demands. The dilemma is genuine because acting on the obligation risks violating epistemic standards, while honoring the constraint risks suppressing safety-critical information in a confirmed-fatality context.
When the prime consultant instructs Engineer A (as sub-consultant) to suppress the wall defect finding, Engineer A's obligation to escalate independently conflicts with the constraint that the prime consultant may possess superior contextual knowledge warranting deference. The tension is genuine because deference to the prime's judgment is professionally reasonable in normal circumstances, yet the suppression instruction in a confirmed-fatality context transforms that deference into complicity. Honoring the deference constraint risks passive acquiescence to suppression; overriding it risks breaching the hierarchical professional relationship and potentially acting on incomplete contextual understanding.
Engineer A is obligated to follow up verbal notification of the wall defect with written confirmation, yet the client has issued a suppression instruction that the constraint framework recognizes must not be complied with. These two elements together create a layered dilemma: the written confirmation obligation is the correct professional response to verbal-only disclosure insufficiency, but producing that written confirmation directly defies the client's explicit suppression instruction. The engineer cannot simultaneously satisfy the client relationship and fulfill the written escalation duty, making this a genuine obligation-versus-constraint conflict where professional ethics override client authority.
Potential tension between Verbal-Only Disclosure Insufficiency Engineer A Wall Defect Public Agency and Engineer A Faithful Agent Client Loyalty Balance Bridge Wall Defect
When the prime consultant instructs Engineer A (as sub-consultant) to suppress the wall defect finding, Engineer A's obligation to escalate independently conflicts with the constraint that the prime consultant may possess superior contextual knowledge warranting deference. The tension is genuine because deference to the prime's judgment is professionally reasonable in normal circumstances, yet the suppression instruction in a confirmed-fatality context transforms that deference into complicity. Honoring the deference constraint risks passive acquiescence to suppression; overriding it risks breaching the hierarchical professional relationship and potentially acting on incomplete contextual understanding.
Engineer A is obligated to follow up verbal notification of the wall defect with written confirmation, yet the client has issued a suppression instruction that the constraint framework recognizes must not be complied with. These two elements together create a layered dilemma: the written confirmation obligation is the correct professional response to verbal-only disclosure insufficiency, but producing that written confirmation directly defies the client's explicit suppression instruction. The engineer cannot simultaneously satisfy the client relationship and fulfill the written escalation duty, making this a genuine obligation-versus-constraint conflict where professional ethics override client authority.
Show 1 other tension
These tensions did not map cleanly to a single character.
Tension between Sub-Consultant Suppression-Instruction Independent Escalation Obligation and Speculative Observation Verbal-Only Subconsultant Escalation Permissibility Constraint
Opening States (10)
Summary
- An engineer's epistemic certainty threshold directly governs the form and channel of required disclosure, with speculative observations permitting verbal-only escalation while confirmed hazards trigger mandatory written documentation.
- A subconsultant's independent escalation obligation does not automatically override a suppression instruction from a prime consultant when the underlying observation lacks sufficient evidentiary confirmation, creating a procedural stalemate rather than a clear ethical violation.
- The distinction between field notes as internal documentation and formal written reports as external escalation tools is ethically significant — omitting a speculative observation from a report may be defensible even when the same observation warrants some form of communication upward.