Step 4: Full View

Entities, provisions, decisions, and narrative

Back to Case
Duty To Report Unrelated Information Observed During Rendering Of Services
Step 4 of 5

210

Entities

4

Provisions

2

Precedents

16

Questions

21

Conclusions

Phase Lag

Transformation
Phase Lag Delayed consequences reveal obligations not initially apparent
A temporal gap opens between Engineer A's present-tense verbal disclosure and the future confirmation (or failure) of corrective action by the public agency. During this gap, the case effectively runs two parallel, unresolved scenarios -- one in which the agency acts promptly (validating Engineer A's silence as ethical) and one in which it does not (retroactively reactivating his duty to escalate). The Board's conclusion is suspended between these parallel tracks rather than settling into a single, final allocation of responsibility.
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

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

II.1.c board + analysis Engineers shall not reveal facts, data, or information without the prior consent of the client or employer except as authorized or required by law or this Code.
How this applies in the case (showing 3 of 22)
Obligation
Engineer A Defect Disclosure Duty
Disclosure of the defect must respect confidentiality rules requiring client consent or legal authorization
Action
Information Relay
Revealing information to another party requires client or employer consent
State
Client Report Omission Directive
This provision addresses whether an engineer may withhold information at a clients request without proper authorization.
Obligation (2)
  • Engineer A Defect Disclosure Duty
    Disclosure of the defect must respect confidentiality rules requiring client consent or legal authorization
  • Engineer A Client Defect Disclosure Duty
    Engineer must balance revealing information to the client with confidentiality obligations under the code
Action (3)
  • Information Relay
    Revealing information to another party requires client or employer consent
  • Omission Request
    Request to omit information relates to unauthorized disclosure or withholding
  • Nonreporting to Authorities
    Not reporting facts to authorities involves disclosure restrictions without consent
State (3)
  • Client Report Omission Directive
    This provision addresses whether an engineer may withhold information at a clients request without proper authorization.
  • No Confidentiality Expectation on Wall Defect
    The provision only restricts disclosure when confidentiality is expected which does not apply here.
  • Wall Defect Report Omission
    Omitting the wall defect from the report implicates the rule against withholding facts without proper consent or legal basis.
Constraint (2)
  • Engineer A Wall Defect Report Suppression
    This provision restricts revealing client information without consent supporting suppression in the report
  • Engineer A Premature Authority Report Ban
    This provision limits disclosure to outside parties absent consent or legal requirement
Principle (3)
  • Loyalty in Report Omission Request
    This provision governs whether the engineer could withhold facts absent client consent making it central to the omission request.
  • Confidentiality Expectation in Present Case
    The provision only restricts disclosure of confidential facts and the Board found the defect information was not confidential.
  • Loyalty in Bridge Defect Case
    Reporting the defect verbally to the client aligns with the requirement to reveal facts appropriately to the employer or client.
Role (2)
  • Engineer A Inspector Engineer
    Engineer A must decide whether client consent is needed before revealing the defect information discovered during service.
  • VWX Prime Consultant Firm
    VWX as the entity receiving and controlling information about the defect must consider confidentiality obligations to its client.
Event (1)
  • Defect Discovery
    Provision governs whether engineer may reveal the defect information found unrelated to original engagement
Resource (4)
  • Engineer A Engineering Notes
    These notes contain client-related facts about the bridge wall that cannot be revealed without consent.
  • BER Case No. 89-7
    This case directly addresses the confidentiality obligation versus disclosure duty.
  • BER Case No. 97-5
    This case applies the same confidentiality principle from Case 89-7.
  • NSPE Code of Ethics
    The Code establishes the nondisclosure rule for client information.
Capability (2)
  • Engineer A Defect Disclosure
    This provision governs whether Engineer A may reveal the defect information without client consent unless required by law
  • Engineer A Obligation Balancing
    Engineer A must balance confidentiality duty to client against public safety when deciding to disclose
II.3.a board + analysis Engineers shall be objective and truthful in professional reports, statements, or testimony. They shall include all relevant and pertinent information in such reports, statements, or testimony, which should bear the date indicating when it was current.
How this applies in the case (showing 3 of 20)
Obligation
Engineer A Defect Disclosure Duty
Reports must be objective and include all relevant information such as the discovered defect
Action
Defect Documentation
Reports must be objective and include all relevant defect information
State
Pavement Inspection Scope Limit
The provision requires all relevant information be included even if outside the original scope of the report.
Obligation (2)
  • Engineer A Defect Disclosure Duty
    Reports must be objective and include all relevant information such as the discovered defect
  • Engineer A Client Defect Disclosure Duty
    Requires full and truthful documentation of the defect for the client record
Action (3)
  • Defect Documentation
    Reports must be objective and include all relevant defect information
  • Report Exclusion Compliance
    Excluding relevant information from a report violates the duty to include all pertinent facts
  • Omission Request
    Requesting omission of information conflicts with the duty to include all relevant facts
State (4)
  • Pavement Inspection Scope Limit
    The provision requires all relevant information be included even if outside the original scope of the report.
  • Wall Defect Report Omission
    Excluding the observed defect violates the duty to include all relevant and pertinent information in reports.
  • Defective Bridge Wall Hazard
    A safety hazard observed during service is relevant information that must be reported truthfully.
  • Client Report Omission Directive
    Following a client directive to omit relevant safety information conflicts with this objectivity requirement.
Constraint (2)
  • Engineer A Speculative Final Report Ban
    This provision requires only relevant and pertinent verified information in reports, excluding speculation
  • Engineer A Wall Defect Report Suppression
    This provision governs what must be included as relevant information in the final report
Principle (3)
  • Expertise-Calibrated Reporting of Defect
    The provision requires including all relevant information in reports which relates to how the defect should be documented.
  • Public Welfare in Bridge Defect Case
    Objective and truthful reporting supports the paramount duty to protect public welfare by disclosing safety-relevant facts.
  • Loyalty in Report Omission Request
    The request to omit the defect conflicts with the duty to include all relevant information in reports.
Role (1)
  • Engineer A Inspector Engineer
    Engineer A must include all relevant information such as the observed defect in professional reports even if outside the original scope.
Event (1)
  • Defect Discovery
    Requires engineer to include all relevant findings such as the discovered defect in reports
Resource (2)
  • Engineer A Final Report
    The final report must include all relevant pertinent information found during inspection.
  • Engineer A Engineering Notes
    The notes document findings that should be objectively reported if relevant.
Capability (2)
  • Engineer A Defect Disclosure
    Requires that Engineer A report the defect truthfully and completely as pertinent information
  • Engineer A Field Note Documentation
    Documenting the defect ensures relevant information is preserved for truthful reporting
III.1.a board + analysis Engineers shall acknowledge their errors and shall not distort or alter the facts.
How this applies in the case (showing 3 of 14)
Obligation
Engineer A Defect Disclosure Duty
Engineer must not distort or hide facts about the defect discovered
Action
Report Exclusion Compliance
Complying with exclusion of facts distorts or alters the truthful record
State
Wall Defect Report Omission
Omitting known facts about the defect constitutes a distortion of the complete factual record.
Obligation (2)
  • Engineer A Defect Disclosure Duty
    Engineer must not distort or hide facts about the defect discovered
  • Engineer A Client Defect Disclosure Duty
    Engineer must acknowledge the defect and not alter the facts when informing the client
Action (2)
  • Report Exclusion Compliance
    Complying with exclusion of facts distorts or alters the truthful record
  • Omission Request
    Omitting known facts constitutes distortion of information
State (2)
  • Wall Defect Report Omission
    Omitting known facts about the defect constitutes a distortion of the complete factual record.
  • Unquantified Wall Defect Surmise
    Engineers must not alter or minimize facts even when the extent of a defect is uncertain.
Constraint (1)
  • Engineer A Field Notes Alteration Ban
    This provision prohibits altering or distorting factual field notes
Principle (2)
  • Loyalty in Report Omission Request
    Agreeing to omit the defect information risks distorting or altering the facts of the engineering record.
  • Confidentiality Expectation in Present Case
    Not distorting facts supports the finding that the defect information could not be treated as suppressible confidential data.
Role (1)
  • Engineer A Inspector Engineer
    Engineer A must not distort or omit the facts regarding the pre-existing defect observed during inspection.
Event (1)
  • Defect Discovery
    Requires engineer to acknowledge the discovered defect rather than distort or ignore it
Resource (1)
  • Engineer A Final Report
    The report must not distort or omit facts about conditions observed.
Capability (2)
  • Engineer A Defect Recognition
    Engineer A must not distort or ignore the facts of the observed defect
  • Engineer A Field Note Documentation
    Accurate documentation of facts prevents distortion or alteration of the record
III.2.b board + analysis Engineers shall not complete, sign, or seal plans and/or specifications that are not in conformity with applicable engineering standards. If the client or employer insists on such unprofessional conduct, they shall notify the proper authorities and withdraw from further service on the project.
How this applies in the case (showing 3 of 13)
Obligation
Engineer A Corrective Action Follow-Through Duty
If proper authorities fail to correct nonconforming conditions engineer must notify them and withdraw if needed
Action
Nonreporting to Authorities
Failure to notify proper authorities when required violates this provision
State
Public Agency Defect Awareness
If the client refuses to act on a nonconforming defect the engineer must notify proper authorities.
Obligation (2)
  • Engineer A Corrective Action Follow-Through Duty
    If proper authorities fail to correct nonconforming conditions engineer must notify them and withdraw if needed
  • Engineer A Public Safety Duty
    Ensuring conformity with engineering standards protects public safety regarding the defective wall
Action (2)
  • Nonreporting to Authorities
    Failure to notify proper authorities when required violates this provision
  • Verbal Safety Reporting
    Verbal reporting of safety defects relates to the duty to notify authorities of nonconformities
State (2)
  • Public Agency Defect Awareness
    If the client refuses to act on a nonconforming defect the engineer must notify proper authorities.
  • Awaiting Public Agency Corrective Action
    This provision supports notifying authorities when the client fails to address a known nonconformity.
Constraint (1)
  • Engineer A Premature Authority Report Ban
    This provision requires notifying proper authorities if unsafe conditions are not addressed by the client
Principle (2)
  • Follow Through on Corrective Action
    This provision requires notifying proper authorities when nonconforming conditions are not addressed, matching the duty to follow through.
  • Public Welfare in Bridge Inspection
    The provision reflects the engineer's duty to act on nonconforming or unsafe conditions discovered even outside the retained scope.
Role (1)
  • VWX Prime Consultant Firm
    VWX as the firm responsible for signing and sealing bridge plans must ensure conformity with engineering standards given the known defect.
Event (2)
  • Bridge Wall Failure
    Provision addresses nonconforming design that led to the wall failure
  • Defect Discovery
    Provision requires reporting defects not conforming to engineering standards once discovered
Capability (1)
  • Engineer A Corrective Action Follow-Through
    If proper authorities fail to act on nonconforming conditions, Engineer A has a duty to notify proper authorities
Cross-Case Connections
View Extraction
Explicit Board-Cited Precedents 1 Lineage Graph

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

Principle Established:

Engineers must balance the obligation to maintain client confidentiality against the paramount obligation to protect public health and safety; failure to report known safety code violations to public authorities, even under a confidentiality agreement, is unethical.

Citation Context:

The Board discusses this prior case at length as an example of the ethical dichotomy between client confidentiality and public safety, then distinguishes its facts from the present case to reach a different conclusion.

Relevant Excerpts
discussion: "An example of this basic ethical dichotomy was considered by the NSPE Board of Ethical Review in Case No. 89-7 (which the Board also applied in Case No. 97-5 )."
discussion: "Turning to the facts in this case, it is the Board’s position that the facts and circumstances in Case No. 89-7 , while somewhat similar in nature, are significantly different than the facts in the present case."
discussion: "Another difference between the two cases is that in Case No. 89-7 , there was a specific agreement between the engineer and the client to maintain the confidentiality of the information."
discussion: "Also in Case No. 89-7 , there was the possibility of a dangerous condition developing at some point in the future, while in the present case, loss of life had already occurred."

Principle Established:

Reaffirms the principle established in Case No. 89-7 regarding the conflict between client confidentiality and the engineer's duty to protect public health and safety.

Citation Context:

The Board notes that the principle from Case No. 89-7 regarding balancing confidentiality against public safety was also applied in this later case.

Relevant Excerpts
discussion: "An example of this basic ethical dichotomy was considered by the NSPE Board of Ethical Review in Case No. 89-7 (which the Board also applied in Case No. 97-5 )."
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 55% Facts Similarity 45% Discussion Similarity 70% Outcome Alignment 100% Tag Overlap 43% Principle Overlap 86%
Same outcome ethical View Synthesis
Component Similarity 60% Facts Similarity 56% Discussion Similarity 66% Outcome Alignment 100% Tag Overlap 22% Principle Overlap 74%
Same outcome ethical View Synthesis
Component Similarity 59% Facts Similarity 49% Discussion Similarity 64% Outcome Alignment 100% Tag Overlap 22% Principle Overlap 61%
Same outcome ethical View Synthesis
Component Similarity 58% Facts Similarity 42% Discussion Similarity 64% Outcome Alignment 100% Principle Overlap 81%
Same outcome ethical View Synthesis
Component Similarity 52% Facts Similarity 50% Discussion Similarity 68% Outcome Alignment 100% Tag Overlap 25% Principle Overlap 70%
Same outcome ethical View Synthesis
Component Similarity 54% Facts Similarity 23% Discussion Similarity 59% Outcome Alignment 100% Tag Overlap 18% Principle Overlap 70%
Same outcome ethical View Synthesis
Component Similarity 55% Facts Similarity 55% Discussion Similarity 92% Outcome Alignment 100% Principle Overlap 79%
Same outcome ethical View Synthesis
Component Similarity 57% Facts Similarity 42% Discussion Similarity 52% Outcome Alignment 100% Tag Overlap 9% Principle Overlap 63%
Same outcome ethical View Synthesis
Component Similarity 52% Facts Similarity 50% Discussion Similarity 71% Outcome Alignment 100% Tag Overlap 12% Principle Overlap 69%
Same outcome ethical View Synthesis
Component Similarity 52% Facts Similarity 43% Discussion Similarity 54% Outcome Alignment 100% Tag Overlap 9% Principle Overlap 66%
Same outcome ethical View Synthesis
Questions & Conclusions (2 board)
View Extraction
Board Board question 1

Was it ethical for Engineer A to retain the information in his engineering notes but not include it in the final report as requested?

Board conclusion It was ethical for Engineer A to retain the information in his engineering notes but not include it in the final written report as requested.
Resolved by: The board treated verbal disclosure through the client chain as sufficient to satisfy the public safety duty, allowing the loyalty owed to VWX's request for a scope-limited written report to govern the form of final documentation. (confidence 0.82)
II.1.c. III.1.a. 3 principles 3 facts Conditions Narrative
Implicit (2)

Does Engineer A's lack of structural engineering expertise affect his obligation to pursue or verify the defective wall condition further, given that his surmise about causation was outside his scope of competence?

AnalyticalEngineer A's lack of structural engineering expertise, combined with the fact that identifying wall defects fell outside his contracted scope, supports the reasonableness of deferring further formal investigation or documentation to the public agency and its structural engineers. However, this expertise gap does not excuse Engineer A from the baseline duty to ensure his tentative safety-relevant observation was communicated with sufficient clarity that it could be understood and acted upon by those with the relevant expertise, since his surmise concerned a defect potentially linked to a fatality.
Resolved by: The board weighs the reasonableness of deferring detailed technical investigation to qualified structural engineers against the non-negotiable baseline duty to communicate safety-relevant surmises clearly enough to be acted upon, especially given the fatality connection. (confidence 0.72)
II.3.a. III.1.a. 2 principles 3 facts Conditions Narrative
AnalyticalRegarding Q101, Engineer A's lack of structural engineering expertise does not relieve him of an obligation to flag the observed wall condition, but it does calibrate the form that obligation takes. Because the surmise about causation exceeded his competence, his duty was satisfied by verbal disclosure to the party positioned to secure qualified structural evaluation (VWX and, through it, the public agency), rather than by asserting a definitive causal finding in a signed, sealed final report he was not competent to certify.
Resolved by: The obligation to flag a public safety hazard was weighed against the limits of the engineer's competence, resolved by requiring disclosure calibrated to what he could responsibly assert rather than a certified causal finding. (confidence 0.82)
II.3.a. III.2.b. 3 principles 3 facts Conditions Narrative

Does the fact that VWX and the public agency were both already informed of the defect (through verbal channels) change the ethical calculus of omitting it from the written report, compared to a scenario where no one else knew?

AnalyticalThe Board's finding that Engineer A acted ethically in retaining but not reporting the defect information rests critically on the fact that verbal disclosure had already reached the public agency through the reporting chain. This is not a case of pure silence but of channeling information through proper organizational lines while declining to formalize it in a document outside his contracted scope. The ethical propriety of the omission is thus conditioned on this prior disclosure having actually occurred and having been effective in reaching decision-makers, not on the mere fact of omission itself.
Resolved by: The board's reasoning implicitly weighs the omission from the report as harmless only because the substantive safety obligation was already discharged through an alternate, effective channel, not because omission itself is presumptively acceptable. (confidence 0.75)
II.1.c. III.1.a. 3 principles 3 facts Conditions Narrative
AnalyticalRegarding Q104, the fact that both VWX and the public agency already possessed the defect information through verbal channels is central to why omission from the written report is ethically permissible: the operative public-safety purpose of disclosure (ensuring the responsible parties know and can act) was already met, distinguishing this case from one where written omission would leave all relevant parties uninformed.
Resolved by: The requirement of written disclosure was weighed against the fact that the safety purpose of disclosure was already achieved through verbal channels, tipping the balance toward permissible omission. (confidence 0.80)
II.1.c. II.3.a. 3 principles 3 facts Conditions Narrative
Principle tension (2)

How should Engineer A balance his duty of loyalty to VWX's request to omit the defect from the final report against his overriding obligation to hold public welfare paramount?

AnalyticalRegarding Q201, Engineer A's compliance with VWX's request represents a permissible subordination of loyalty to a narrower documentation preference, not a subordination of public welfare, because the substantive safety information had already been transmitted through verbal channels before the loyalty-driven omission request was made; loyalty governs only the form of the report, while public welfare is satisfied through prior disclosure.
Resolved by: Loyalty to VWX's documentation preference was weighed against the paramount duty to public welfare and found not to conflict, because the substantive safety disclosure had already occurred before the loyalty-driven request was made. (confidence 0.85)
II.1.c. II.3.a. 3 principles 3 facts Conditions Narrative
AnalyticalThe apparent tension between Loyalty in Report Omission Request and Public Welfare in Bridge Inspection was resolved not by subordinating one to the other, but by functionally separating the channel of disclosure from the channel of documentation. Engineer A satisfied the public welfare principle through verbal disclosure up the chain (to VWX and then the public agency), which allowed him to honor the loyalty-based request to exclude the matter from the formal written report without truly compromising safety. This suggests that in this case type, the Board treats 'public welfare paramount' as a duty to ensure someone with authority is informed and positioned to act, not necessarily a duty to control the form or venue of every report.
Resolved by: The board avoided ranking loyalty against public welfare by splitting the obligation into two independent channels, satisfying public welfare through verbal disclosure while satisfying loyalty through documentary omission. (confidence 0.80)
II.3.a. 3 principles 3 facts Conditions Narrative

Is there a tension between expertise-calibrated reporting of the defect (since Engineer A lacked structural expertise) and public welfare in the bridge defect case, which might demand disclosure regardless of confidence level?

AnalyticalExpertise-Calibrated Reporting of Defect and Public Welfare in Bridge Defect Case were reconciled through a threshold approach: Engineer A's lack of structural expertise justified limiting his written report to a mere surmise rather than a definitive technical finding, but it did not excuse him from raising the issue at all. The Board's endorsement of his verbal disclosure, despite acknowledging it was 'outside his scope,' indicates that competence limitations narrow the form and certainty of required reporting but do not eliminate the underlying duty to flag observed risks to those with the expertise and authority to evaluate them.
Resolved by: The board balanced competence limitations against the disclosure duty by allowing reduced certainty and informal form of reporting while still requiring that the risk be flagged to those with relevant expertise and authority. (confidence 0.79)
II.3.a. 3 principles 3 facts Conditions Narrative
Theoretical (2)

From a deontological perspective, did Engineer A fulfill his duty to hold paramount public safety by verbally reporting the defect, even though he complied with the request to omit it from the final written report?

AnalyticalRegarding Q301, from a deontological standpoint Engineer A discharged his duty to hold public safety paramount through the act of verbal disclosure itself, since the duty attaches to ensuring relevant parties are informed rather than to the specific medium (written report) used to convey the information; his compliance with the omission request therefore does not violate the underlying duty, provided the verbal channel functioned as an adequate substitute.
Resolved by: The board subordinated the medium of disclosure to the fact of disclosure, treating the duty to hold safety paramount as satisfied by informing relevant parties regardless of report format. (confidence 0.75)
II.3.a. 2 principles 3 facts Conditions Narrative

Did Engineer A act with professional integrity by simultaneously preserving the defect information in his engineering notes (refusing to erase it) while agreeing not to formally document it in his final report?

AnalyticalRegarding Q303, Engineer A's dual action of preserving the defect in his engineering notes while omitting it from the final report reflects a coherent integrity-preserving strategy: retaining the notes ensures the factual record cannot later be characterized as altered or destroyed (satisfying the prohibition on distorting facts), while the omission from the formal deliverable respects the scope-of-work boundary agreed upon with the client.
Resolved by: The board balanced the duty not to distort facts against the duty of faithful agency to the client's scope-of-work request, finding both satisfied because the notes preserved truth while the report respected contractual boundaries. (confidence 0.80)
III.1.a. III.2.b. 2 principles 3 facts Conditions Narrative
Counterfactual (2)

If Engineer A had not verbally reported the defect to VWX at all, would the Board still have found it ethical for him to omit the information from his final report and refrain from notifying other authorities?

If identifying wall defects had been within Engineer A's original scope of work rather than outside it, would the Board still have found it ethical for him to exclude the defect from his final written report at VWX's request?

AnalyticalRegarding Q403, had wall-defect identification been within Engineer A's original scope of work, the Board would likely have reached a different conclusion on Q1, since VWX's request to omit the finding from the final report would then constitute a request to falsify or incompletely report a matter within his professional scope, directly implicating the prohibition on distorting facts in signed engineering documents rather than merely accommodating a scope boundary.
Resolved by: The board treated the scope boundary as tipping the balance toward permissible omission, reasoning that inclusion within scope would instead trigger the stronger prohibition against distorting facts in a professionally signed document. (confidence 0.78)
III.1.a. II.3.a. 3 principles 3 facts Conditions Narrative
Board Board question 2

Was it ethical for Engineer A not to report this information to any other public agency or authority?

Board conclusion It was ethical for Engineer A not to report this information to any other public agency or authority as long as corrective action is taken by the public agency within a relatively short period of time.
Resolved by: The board allowed loyalty to the client's confidentiality interests and the informal reporting chain to excuse independent notification to other authorities, but only insofar as that deference did not compromise actual correction of the hazard within a short timeframe. (confidence 0.85)
II.1.c. 3 principles 3 facts Conditions Narrative
Implicit (1)

What ongoing duty, if any, does Engineer A have to monitor whether the public agency actually takes corrective action on the wall defect, given that he only verbally relayed the information and did not track its resolution?

AnalyticalThe Board's second conclusion is explicitly conditional: nonreporting to other authorities is ethical 'as long as corrective action is taken within a relatively short period of time.' This conditionality implies an ongoing duty on Engineer A's part to monitor the situation, at least informally, since his ethical clearance is time-limited and contingent on facts outside his direct control. The Board does not specify what mechanism, if any, obligates Engineer A to follow up, creating a gap between the conditional ethical standard and any concrete monitoring obligation.
Resolved by: The board balances the practical limits of Engineer A's authority and expertise against the ongoing public welfare stake by implying a soft, informal monitoring expectation rather than a hard, enforceable follow-up duty. (confidence 0.70)
2 principles 3 facts Conditions Narrative
AnalyticalRegarding Q102, Engineer A's obligations do not end with the initial verbal relay. Although his written duty is discharged, his ethical exposure remains contingent on the public agency's follow-through; he retains at least a residual monitoring interest such that if he becomes aware corrective action is not forthcoming, his duty to report to another authority is reactivated, consistent with the Board's qualification that silence is ethical only 'as long as corrective action is taken within a relatively short period of time.'
Resolved by: The discharged written obligation was weighed against an ongoing public welfare interest, resulting in a residual monitoring duty that activates only if the agency's corrective response is not forthcoming. (confidence 0.78)
II.3.a. 3 principles 3 facts Conditions Narrative
Principle tension (1)

How should the principle of follow-through on corrective action be balanced against loyalty in the bridge defect case, if the public agency delays or fails to act on the defect after Engineer A has already deferred to VWX's request?

AnalyticalRegarding Q203, if the public agency fails to act within a reasonable time, the balance the Board struck between loyalty and follow-through would tip decisively toward an affirmative duty to escalate reporting to another authority, since continued deference to VWX's request in the face of known inaction would convert an ethically neutral documentation accommodation into an ethically culpable failure to hold public safety paramount.
Resolved by: The board treated loyalty to VWX's documentation request as conditionally acceptable only so long as it did not obstruct actual correction, so continued inaction by the agency shifts the balance toward the paramount safety obligation. (confidence 0.80)
II.1.c. III.1.a. 3 principles 3 facts Conditions Narrative
AnalyticalThe Board's conditional phrasing -- ethical 'as long as corrective action is taken...within a relatively short period of time' -- reveals that Follow Through on Corrective Action functions as a latent, unresolved principle rather than a settled one. Loyalty and scope-of-work deference were allowed to govern Engineer A's immediate conduct, but the ethical permissibility of his ongoing silence toward other authorities remains contingent on an external event (agency action) that Engineer A has no established duty or mechanism to monitor. This exposes a structural gap: the case resolves the initial disclosure dilemma but leaves open how principle prioritization should shift if the condition triggering continued silence is never verified or fails to materialize.
Resolved by: The board allowed loyalty to VWX and deference to scope-of-work boundaries to govern Engineer A's immediate silence toward other authorities, while treating public welfare as provisionally satisfied only on the unverified assumption that the public agency would act within a short period. (confidence 0.75)
II.1.c. II.3.a. 3 principles 3 facts Conditions Narrative
Theoretical (1)

From a consequentialist perspective, does the fact that the public agency was made aware and could take corrective action justify Engineer A's decision not to independently report the defect to any other authority?

AnalyticalRegarding Q302, a consequentialist analysis supports the Board's finding: because the public agency—the entity with authority and resources to remediate the defect—was already informed and positioned to act, reporting to an additional authority would have produced marginal safety benefit while imposing costs (redundant investigations, strained professional relationships) that outweigh the incremental protective value, justifying nonreporting so long as timely correction follows.
Resolved by: The board weighed the marginal safety benefit of reporting to a further authority against the costs of redundant investigation and strained professional relationships, finding the incremental benefit insufficient to require additional reporting. (confidence 0.75)
II.1.c. 2 principles 3 facts Conditions Narrative
Counterfactual (1)

If the public agency failed to take corrective action on the defective wall within a relatively short period of time, would the Board still conclude that Engineer A's silence toward other authorities was ethical?

AnalyticalRegarding Q401, if the public agency did not take corrective action within a relatively short period, the Board's conclusion that silence toward other authorities was ethical would no longer hold; the ethical permissibility explicitly hinges on the contingency of timely correction, so prolonged inaction would obligate Engineer A to report the defect to another appropriate agency to fulfill his overriding public safety duty.
Resolved by: The board subordinated loyalty-based silence to the paramount public safety duty once the timeliness condition underlying that silence's permissibility is no longer satisfied. (confidence 0.82)
3 principles 3 facts Conditions Narrative
Analytical questions (2)

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

Implicit (1)

Should the fact that Police Officer B died in an accident possibly linked to the defect create a heightened, non-waivable disclosure duty distinct from ordinary bridge inspection findings?

AnalyticalRegarding Q103, the fatal accident does not create a separate categorical disclosure duty beyond the ordinary public-welfare obligation already governing bridge inspection; rather, it heightens the practical urgency and moral stakes of ensuring the verbal disclosure was actually acted upon, since the consequence of inaction (another failure) is now demonstrated rather than speculative.
Resolved by: The demonstrated harm from the fatal accident was weighed against the pre-existing disclosure obligation, concluding that the accident intensifies urgency rather than creating a distinct duty. (confidence 0.75)
II.3.a. 3 principles 3 facts Conditions Narrative
Principle tension (1)

Does the principle of confidentiality expectation in this case conflict with the principle of public welfare in bridge inspection when the withheld information concerns a safety-critical structural defect rather than routine business information?

AnalyticalRegarding Q202, no genuine conflict between confidentiality and public welfare arises here because the withheld information was never treated as confidential in the sense contemplated by Code section II.1.c.; it was voluntarily shared with the client and the public agency, meaning the omission from the final report is a documentation choice rather than an act of concealment implicating the confidentiality-versus-safety tension seen in cases like BER 89-7 and 97-5.
Resolved by: The board found no true competition between confidentiality and public welfare because the predicate condition for invoking confidentiality, namely that the information was being kept secret, was absent. (confidence 0.85)
II.1.c. 2 principles 3 facts Conditions Narrative
AnalyticalConfidentiality Expectation in Present Case did not actually generate a genuine conflict with public welfare, because the information was never confidential in substance -- it had already been relayed verbally to the client and the public agency itself. The real principle at stake was scope-of-work fidelity (Engineer A was not retained to assess structural wall defects) rather than nondisclosure of proprietary or protected information. This reframing shows that what looks like a classic 'confidentiality versus public safety' dilemma (as in Case 89-7 and Case 97-5) can dissolve once it is recognized that the relevant audience already possesses the safety-critical facts; the remaining question becomes one of formal documentation and professional boundaries, not disclosure ethics.
Resolved by: The board dissolved the apparent confidentiality-versus-safety conflict by reclassifying the issue as one of scope fidelity rather than nondisclosure, since the safety-critical facts were already known to the relevant parties. (confidence 0.77)
II.1.c. 3 principles 3 facts Conditions Narrative
Decisions & Arguments (5)
View Extraction

Should Engineer A include the observed wall defect in his final written report to VWX, or document it only in field notes and convey it verbally to the client?

Options considered:
O1 Document the defect observation in field notes without alteration and report it verbally to the client, while excluding it from the signed final report as requested. Board's choice
O2 Formally document the wall defect observation in the signed final report despite it falling outside the contracted pavement inspection scope, to create an official record.
O3 Confine all documentation and communication strictly to pavement findings, omitting the wall observation from field notes, verbal reports, and the final report entirely.
Argument structure (Toulmin):
Grounds

Engineer A discovered an apparent pre-existing wall defect while performing a pavement inspection outside his contracted scope. VWX asked him to omit it from the final report. He kept it in his field notes and told VWX verbally.

Warrant

Engineers must hold paramount the safety of the public, which requires that safety-relevant observations be communicated to someone able to act on them; engineers must also act as faithful agents of their clients and must not certify in a signed document matters outside their contracted scope and competence.

Rebuttal

This resolution would not apply if the verbal report to VWX was not an adequate substitute for written documentation, or if Engineer A's lack of structural expertise meant the observation could not be understood or acted upon without more formal documentation.

Engineer A Client Defect Disclosure Duty

Should Engineer A rely on the public agency already informed of the defect to take corrective action, or independently report the defect to another public authority?

Options considered:
O1 Trust that the public agency, already informed through VWX, has the authority and responsibility to remediate the defect and refrain from separately notifying other authorities. Board's choice
O2 Notify a state engineering board or independent safety authority directly about the observed defect, regardless of the public agency's awareness.
O3 Seek out higher-level officials within the same public agency to confirm the defect report was received and will be acted upon.
Argument structure (Toulmin):
Grounds

Engineer A verbally informed VWX, which relayed the defect information to the public agency responsible for the bridge. Engineer A did not separately notify any other public authority.

Warrant

Engineers must hold paramount public safety, but this duty is discharged once information reaches an entity with authority and resources to act, and engineers should follow through to see that correct action is taken only if the responsible agency fails to act.

Rebuttal

This reliance would not be justified if the public agency lacked authority, resources, or intent to act, or if Engineer A had reason to believe the defect would not be timely addressed.

Engineer A Corrective Action Follow-Through Duty

Should Engineer A limit his role to flagging the observed defect to qualified parties, or pursue independent investigation and verification despite lacking structural expertise?

Options considered:
O1 Report the tentative observation and surmised cause to the client and public agency for evaluation by structural engineers, without personally certifying a finding. Board's choice
O2 Personally investigate the wall's structural condition and probable cause despite lacking structural training and contracted authority to do so.
O3 Decline to mention the observation to anyone until a definitive, expert-verified cause can be established, since the surmise exceeds his competence.
Argument structure (Toulmin):
Grounds

Engineer A observed an apparent wall defect during a pavement inspection but had no structural engineering training and could not verify the cause of the condition.

Warrant

Engineers shall undertake only work for which they are qualified by training or experience, and reporting obligations must be calibrated to the reporter's expertise while still requiring that observed risks be communicated to those able to evaluate them.

Rebuttal

The expertise-calibrated limitation would not apply if the defect posed an obvious and imminent danger recognizable without structural training, in which case more assertive action would be required regardless of competence.

Engineer A Defect Disclosure Duty

Should Engineer A actively monitor whether the public agency takes corrective action on the defect, or treat his duty as fully discharged once he made the initial verbal report?

Options considered:
O1 Periodically check whether the public agency has acted on the defect and report to another authority if corrective action is not taken within a reasonable time. Board's choice
O2 Treat the obligation as fully satisfied once the defect was verbally relayed to VWX and the public agency, without further tracking of outcomes.
O3 Ask the public agency or VWX for written or verbal confirmation of a corrective action timeline to create an accountable record.
Argument structure (Toulmin):
Grounds

Engineer A relayed the defect information verbally to VWX and the public agency but did not track or confirm whether corrective action was subsequently taken.

Warrant

Engineers must follow through to see that correct action is taken by the responsible party, and only if that party fails to act should the engineer consider reporting to another authority.

Rebuttal

The monitoring duty would not apply if the public agency's awareness and authority over the bridge were themselves sufficient to fully discharge Engineer A's responsibility without further tracking.

Engineer A Corrective Action Follow-Through Duty

Should the officer's fatality prompt Engineer A to take additional disclosure action beyond his original verbal report, or does his existing disclosure remain sufficient absent a confirmed causal link?

Options considered:
O1 Continue relying on the prior verbal disclosure to VWX and the public agency, since causation between the defect and the fatality remains unconfirmed. Board's choice
O2 Proactively contact the authority investigating Officer B's death to disclose the previously observed wall defect given its possible relevance.
O3 Seek an independent structural assessment to establish whether the defect caused the accident before deciding on further disclosure.
Argument structure (Toulmin):
Grounds

Police Officer B died in an accident possibly linked to the wall defect after Engineer A had already verbally disclosed the defect to VWX and the public agency.

Warrant

Engineers must hold paramount public safety, which requires ensuring that safety-relevant disclosures already made are acted upon, but does not by itself create a new categorical duty beyond that already discharged absent confirmed causation.

Rebuttal

This claim would not hold if the causal link between the defect and the officer's death were confirmed and the public agency had failed to act, in which case a heightened, non-waivable duty to escalate would apply.

Engineer A Public Safety Duty
Event Timeline (12)
12 sequenced 8 actions 4 events
Case timeline
While traveling across the bridge, Police Officer B loses control of his patrol car, which then crashes into the bridge wall.
The bridge wall fails to restrain the crashing patrol car, allowing the vehicle to leave the bridge. A pre-existing defective condition in the wall may have been a contributing factor.
State changes (1)
  • began: Defective Bridge Wall Hazard
Police Officer B's vehicle falls from the bridge to the river below after the wall fails, killing him.
The public agency retains VWX Architects and Engineers to perform a major scheduled overhaul of a bridge.
Causal-normative reasoning(confidence 0.60)
Consultant Retention carries no direct normative weight itself, but it initiates the causal sequence that ultimately places Engineer A in a position to discover and later withhold information about the bridge wall defect, so its significance lies entirely in enabling everything downstream.
State changes (1)
  • began: Prime Consultant Informed Evaluation Position
VWX Architects and Engineers retains Engineer A as its subconsultant with a scope limited solely to identifying pavement damage on the bridge and reporting it to VWX.
Causal-normative reasoning(confidence 0.65)
Subconsultant Retention is normatively neutral on its own, yet it is the direct cause of Defect Discovery, making it the pivotal structural step that brings the safety issue into existence for the engineers to grapple with ethically.
During his bridge inspection, and outside his retained scope of pavement damage identification, Engineer A notices an apparent pre-existing defective condition in the wall near the site of the fatal accident.
State changes (1)
  • began: Unquantified Wall Defect Surmise
While conducting the inspection, Engineer A notices an apparent pre-existing defective condition in the bridge wall near the accident site, surmises it may have contributed to the wall failure, and records this observation in his engineering notes even though it is outside his scope of work.
At stake (1)
  • Obligation to hold paramount the public health and safety
Causal-normative reasoning(confidence 0.60)
Defect Documentation is guided by the obligation to hold paramount public health and safety, reflecting that recording the wall's condition is the professional's way of honoring that duty even though it is not itself the act that reaches the client or public.
State changes (1)
  • began: Unquantified Wall Defect Surmise
Engineer A verbally reports the observed defective wall condition to his client, VWX Architects and Engineers.
Fulfills (2)
  • Obligation to hold paramount the public health and safety
  • Obligation to be faithful to the client
Causal-normative reasoning(confidence 0.75)
Verbal Safety Reporting fulfills both the obligation to hold paramount public health and safety and the obligation to be faithful to the client because it discloses the defect to the responsible party, yet its downstream effects through Information Relay and Omission Request show the tension between those two obligations once the client-aligned agency chooses to have the defect omitted from formal reporting.
State changes (1)
  • began: Client Report Omission Directive
VWX Architects and Engineers verbally reports the defect information received from Engineer A to the public agency.
Fulfills (1)
  • Obligation to hold paramount the public health and safety
Causal-normative reasoning(confidence 0.75)
By relaying Engineer A's verbal safety findings to the public agency, VWX satisfies the paramount duty to public safety in the moment, but this same act sets in motion the Omission Request that later pressures Engineer A into excluding the defect from the written report, showing that an initially safety-serving disclosure can become the causal seed of subsequent nondisclosure.
State changes (2)
  • began: Awaiting Public Agency Corrective Action
  • began: Public Agency Defect Awareness
After the public agency contacts VWX, VWX contacts Engineer A and asks him not to include the defect information in his final report because it was not part of his scope of work.
Causal-normative reasoning(confidence 0.70)
The Omission Request has no violates or fulfills recorded for itself, but because it causes Report Exclusion Compliance and thereby Nonreporting to Authorities, it functions as the hinge where a public agency's and firm's instruction converts an engineer's prior faithful safety disclosure into eventual silence toward regulators.
State changes (1)
  • began: Client Report Omission Directive
Engineer A agrees to omit the defect information from his final report while retaining the information in his engineering notes, as requested by VWX.
Fulfills (2)
  • Obligation to be faithful to the client
  • Obligation to hold paramount the public health and safety
Causal-normative reasoning(confidence 0.80)
Complying with the agency's request to omit the wall defect from the written report is framed as fulfilling both faithfulness to the client and public safety obligations, yet this compliance directly causes the downstream Nonreporting to Authorities, meaning the formal satisfaction of these duties at the reporting stage effectively forecloses independent safety oversight and leaves the wall's hazardous condition unaddressed by regulators.
Engineer A refrains from reporting the defect information to any other public agency or authority, an omission the Board evaluates and finds reasonable at this stage since the observation was speculative and corrective action by the public agency had not yet been assessed.
Fulfills (1)
  • Obligation to be faithful to the client and not disclose confidential information without consent
Causal-normative reasoning(confidence 0.70)
Engineer A's decision not to report the defect to authorities is justified as fulfilling client confidentiality obligations, but because this omission follows directly from the excluded report and precedes the wall's failure and the officer's fatality, it illustrates how strict adherence to client-faithfulness can causally align with, though not be formally blamed for, a tragic outcome that public-safety paramountcy was meant to prevent.
State changes (1)
  • began: Awaiting Public Agency Corrective Action
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 civil engineer retained by VWX Architects and Engineers as a subconsultant to perform bridge inspection services ahead of a major scheduled overhaul. Your scope of work is limited to identifying pavement damage on the bridge deck and reporting it to VWX for further review and repair. Three months ago, Police Officer B lost control of his patrol car on this bridge, crashed into the bridge wall, and died when the wall failed to restrain the vehicle from falling into the river below. While conducting your pavement inspection, you noticed an apparent pre-existing defective condition in the wall near the location of that fatal accident, a condition outside your assigned scope of work. You recorded this observation in your engineering notes and verbally reported it to VWX, who passed the information to the public agency. The public agency then asked VWX, who in turn asked you, not to include this information in your final written report since it falls outside your contracted scope. You must now decide how to proceed with documentation, disclosure, and any further action regarding this defect.

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.

Engineer A Roles in this case: Inspector Engineer

Engineer A's duty to protect public safety conflicts with a constraint that pressures suppression of the wall defect finding, since withholding the defect from a report could leave a hazardous condition unaddressed even though the engineer's professional obligation is to ensure the public is not endangered by known structural problems.

Engineer A's duty to act as a faithful, loyal agent to the VWX firm and its client conflicts with the obligation to disclose the defect to the client, since full disclosure may embarrass the firm, create liability, or contradict the client's preferred narrative, forcing a choice between institutional loyalty and transparent professional communication.

Engineer A's duty to follow through and confirm that corrective action is actually taken on the defect conflicts with the constraint against reporting prematurely to authorities, since if the client or firm delays or ignores remediation, the engineer is limited in how quickly they can escalate the matter to outside parties who could compel a fix.

Police Officer B Roles in this case: Affected Public

Engineer A's duty to protect public safety conflicts with a constraint that pressures suppression of the wall defect finding, since withholding the defect from a report could leave a hazardous condition unaddressed even though the engineer's professional obligation is to ensure the public is not endangered by known structural problems.

Engineer A's duty to follow through and confirm that corrective action is actually taken on the defect conflicts with the constraint against reporting prematurely to authorities, since if the client or firm delays or ignores remediation, the engineer is limited in how quickly they can escalate the matter to outside parties who could compel a fix.

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

Engineer A's duty to protect public safety conflicts with a constraint that pressures suppression of the wall defect finding, since withholding the defect from a report could leave a hazardous condition unaddressed even though the engineer's professional obligation is to ensure the public is not endangered by known structural problems.

Engineer A's duty to act as a faithful, loyal agent to the VWX firm and its client conflicts with the obligation to disclose the defect to the client, since full disclosure may embarrass the firm, create liability, or contradict the client's preferred narrative, forcing a choice between institutional loyalty and transparent professional communication.

The Board’s deliberation

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

It was ethical for Engineer A to retain the information in his engineering notes but not include it in the final written report as requested.
It was ethical for Engineer A not to report this information to any other public agency or authority as long as corrective action is taken by the public agency within a relatively short period of time.
Opening States (10)
Pavement Inspection Scope Limit Defective Bridge Wall Hazard Unquantified Wall Defect Surmise Client Report Omission Directive Wall Defect Report Omission Public Agency Defect Awareness No Confidentiality Expectation on Wall Defect Engineer A Structural Expertise Gap Awaiting Public Agency Corrective Action Prime Consultant Informed Evaluation Position
Summary
  • Engineers may satisfy their ethical duty to document safety concerns by preserving them in personal or project notes even when a client or firm restricts what appears in the final written report.
  • The resolution treats retention of records as a form of partial compliance that protects the engineer's professional integrity without forcing an immediate confrontation with the client or firm over full public disclosure.
  • This approach effectively defers rather than resolves the tension between institutional loyalty and public safety, since the engineer's private notes provide no guarantee that the defect will actually be corrected.

© Licensed under the GNU GPL v3