Step 4: Review
Review extracted entities and commit to OntServe
Commit to OntServe
Phase 2A: Code Provisions
code provision reference 4
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.
DetailsEngineers 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.
DetailsEngineers shall acknowledge their errors and shall not distort or alter the facts.
DetailsEngineers 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.
DetailsPhase 2B: Precedent Cases
precedent case reference 2
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.
DetailsThe Board notes that the principle from Case No. 89-7 regarding balancing confidentiality against public safety was also applied in this later case.
DetailsPhase 2C: Questions & Conclusions
ethical conclusion 21
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.
DetailsIt 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.
DetailsThe 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.
DetailsThe 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.
DetailsEngineer 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.
DetailsRegarding 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.
DetailsRegarding 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.'
DetailsRegarding 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.
DetailsRegarding 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.
DetailsRegarding 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.
DetailsRegarding 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.
DetailsRegarding 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.
DetailsRegarding 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.
DetailsRegarding 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.
DetailsRegarding 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.
DetailsRegarding 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.
DetailsRegarding 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.
DetailsThe 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.
DetailsConfidentiality 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.
DetailsExpertise-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.
DetailsThe 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.
Detailsethical question 16
Was it ethical for Engineer A to retain the information in his engineering notes but not include it in the final report as requested?
DetailsWas it ethical for Engineer A not to report this information to any other public agency or authority?
DetailsDoes 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?
DetailsWhat 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?
DetailsShould 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?
DetailsDoes 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?
DetailsHow 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?
DetailsDoes 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?
DetailsHow 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?
DetailsIs 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?
DetailsFrom 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?
DetailsFrom 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?
DetailsDid 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?
DetailsIf 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?
DetailsIf 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?
DetailsIf 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?
DetailsPhase 2E: Rich Analysis
causal normative link 8
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.
DetailsSubconsultant 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.
DetailsThe 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.
DetailsDefect 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.
DetailsVerbal 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.
DetailsBy 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.
DetailsComplying 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.
DetailsEngineer 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.
Detailsquestion emergence 16
The question arises because Engineer A satisfied public safety through verbal disclosure and truthful notes while still complying with the client's scope limiting request, leaving unresolved whether documentation practice alone (as opposed to verbal notification) is what discharges the paramountcy obligation.
DetailsThe question arises because Engineer A's dual role as inspector bound by client confidentiality and as an engineer bound to hold public safety paramount produces conflicting obligations once the client directed exclusion of the defect from the report and no other authority was informed.
DetailsThe question arises because Engineer A's surmise about the wall's defective condition and its cause fell outside his documented scope and competence (Pavement Inspection Scope Limit, Engineer A Structural Expertise Gap), creating ambiguity about how far his disclosure duty extends when he is not the appropriate expert to confirm the hazard.
DetailsThe question emerges because Engineer A's action of verbal disclosure without documentation or follow-up leaves an ambiguous boundary between an engineer's duty to report and a duty to ensure remediation, especially after the events show the hazard was never fixed.
DetailsThis question emerges because an intervening tragic event (Officer Fatality) retroactively recontextualizes a previously ambiguous engineering judgment (Unquantified Wall Defect Surmise) as a matter with life-safety consequences, forcing reconsideration of whether the original balance between Loyalty in Report Omission Request and Public Welfare in Bridge Defect Case still holds.
DetailsThe question arises because the existence of parallel verbal awareness by both the client and the public agency creates ambiguity about whether the omission from the written report constitutes a genuine safety failure or a harmless redundancy, since the underlying facts were already known through other channels.
DetailsThe question emerges because a single set of facts, a defect found outside the contracted scope that the client wants omitted, simultaneously triggers a duty of faithful agency and a duty to hold public safety paramount, and the ambiguity over the defect's severity and the report's proper scope prevents a clean resolution of which warrant should govern.
DetailsThe question arises because the withheld information sits at the boundary between ordinary confidential client data and a public safety hazard, so it is unclear which warrant, confidentiality or paramount public welfare, governs Engineer A's reporting obligation.
DetailsThe question arises because deference to VWX resolved the immediate reporting conflict but did not guarantee the agency would act, leaving open whether Engineer A's obligation ends at initial disclosure or extends to monitoring outcomes.
DetailsThe question arises because Engineer A's Unquantified Wall Defect Surmise sits at the intersection of two obligations, one urging restraint due to lack of structural expertise and the other urging disclosure because public safety may be at stake, and the tragic outcome exposes the cost of resolving that tension in favor of restraint.
DetailsThe question arises because Engineer A's actions split his duties, satisfying loyalty to the client through report omission while only partially satisfying public safety through verbal notice, leaving it unresolved which warrant should dominate when both are nominally honored.
DetailsThe question arises because the data shows Engineer A took a partial action (informing the agency) that could satisfy a narrow duty-fulfilled warrant, but the subsequent failure and fatality retroactively expose whether that action was consequentially sufficient under the paramount safety principle.
DetailsThe question arises because Engineer A's split behavior of retaining the defect in his private notes while agreeing to its exclusion from the client deliverable looks like a compromise between two obligations, and it is unclear whether this compromise fully discharges either the duty to the public or the duty to the client, or only partially satisfies both.
DetailsThe question arises because the Board's original conclusion assumed the public agency would act on the disclosed defect, and the hypothetical of agency inaction exposes that the original ethical judgment was contingent rather than absolute, since the death of Officer B illustrates the real cost of unaddressed defects.
DetailsThis counterfactual question arises because the case facts bundle two distinct acts, verbal disclosure to VWX and omission from the written report, and it is unclear whether the Board's ethical approval depended on the first act having occurred at all.
DetailsThis question arises because the Board's original ruling rested partly on the defect being outside Engineer A's scope of work, so altering that fact tests whether the ethical conclusion depended on scope or on the more fundamental duty to hold public safety paramount.
Detailsresolution pattern 21
Given that Engineer A lacked structural expertise, that identifying wall defects was outside his contracted pavement inspection scope, and that he had already verbally informed VWX who relayed it to the public agency, the board concluded that omitting the surmise from the formal written report while preserving it in his notes satisfied both his duty to the public and his duty of faithful service to the client.
DetailsGiven that the public agency already possessed the defect information and was positioned to act, the board concluded that Engineer A need not separately notify other authorities, but conditioned this conclusion explicitly on prompt corrective action being taken.
DetailsBecause the board's ethical clearance depends on the fact that decision-makers already had the information, the conclusion would not extend to a case of pure silence, making the finding of ethicality conditional on the prior verbal disclosure having been real and effective.
DetailsBecause the board tied ethical clearance to a temporal condition without naming an enforcement mechanism, the analysis concludes that Engineer A retains at least an informal, ill-defined obligation to remain aware of whether correction occurs, leaving a gap between the conditional standard and any concrete monitoring duty.
DetailsGiven that Engineer A was not a structural engineer and that identifying wall defects was outside his contracted scope, the board reasoned that deferring formal investigation to the public agency's structural engineers was reasonable, but this did not relieve him of the baseline duty to ensure his surmise was clearly conveyed given its possible link to a fatal accident.
DetailsGiven that Engineer A's surmise about the wall's cause exceeded his structural competence, the board concluded his duty to flag the condition was satisfied by verbal disclosure to VWX and the public agency rather than by certifying a definitive causal finding he was not qualified to make.
DetailsGiven that Engineer A only verbally relayed the defect without tracking its resolution, the board concluded his written duty was discharged but his ethical exposure remains contingent on the agency's timely follow-through.
DetailsGiven that the fatal accident occurred after Engineer A had already verbally disclosed the defect, the board concluded it heightened the moral stakes of ensuring that disclosure was acted upon rather than generating a new categorical duty.
DetailsGiven that VWX and the public agency were already aware of the defect through verbal disclosure, the board concluded that omitting it from the written report did not undermine the public safety purpose that disclosure is meant to serve.
DetailsGiven that Engineer A had already verbally disclosed the defect before VWX asked him to omit it from the final report, the board concluded that complying with the request subordinated only the form of documentation to loyalty, not the substance of public welfare.
DetailsGiven that Engineer A had already told VWX and the public agency about the defect, the board concluded that omitting it from the written report was a documentation choice rather than concealment, so the classic confidentiality versus public safety conflict simply did not arise on these facts.
DetailsGiven that Engineer A's initial nonreporting was justified only by an assumption that the public agency would remediate the defect, the board reasoned that if that assumption were proven false through prolonged inaction, the earlier documentation accommodation would no longer be tenable and an affirmative duty to escalate would arise.
DetailsGiven that Engineer A verbally informed both VWX and the public agency of the defect, the board concluded that the deontological duty to prioritize public safety was discharged through that act of communication, independent of whether the written report also contained the finding.
DetailsGiven that the entity with the actual power to fix the wall defect already knew about it, the board reasoned that reporting elsewhere would add cost without meaningfully improving safety outcomes, so nonreporting was justified as long as correction eventually followed.
DetailsGiven that Engineer A kept the defect documented in his own notes without alteration while leaving it out of a report limited to pavement findings, the board concluded this dual approach preserved both factual integrity and appropriate deference to the client's scope, avoiding any violation of the prohibition on distorting facts.
DetailsGiven that the board's approval of Engineer A's silence rested on an implicit assumption of prompt agency correction, it reasoned that if that assumption failed to materialize, the underlying public safety duty would reassert itself and require escalation beyond the informed agency.
DetailsGiven that the wall defect was outside Engineer A's original assignment, the board concluded the omission request was ethically tolerable, but it signaled that the same request would become a facts-distortion violation had the defect fallen within his contracted scope.
DetailsGiven that Engineer A verbally informed both his client and the public agency of the defect, the board reasoned that the paramount public welfare duty was discharged through that channel, freeing him to honor the loyalty-based request to omit the matter from the written report without a genuine conflict.
DetailsGiven that both VWX and the public agency already knew of the defect through verbal disclosure, the board concluded there was no substantive confidentiality interest at stake, and the real question became one of professional scope and documentation rather than disclosure ethics akin to Cases 89-7 and 97-5.
DetailsGiven that Engineer A's structural expertise gap prevented him from making a definitive written finding, the board concluded his obligation was satisfied through a verbal surmise to competent parties, showing that limited competence changes how a risk is reported but not whether it must be reported at all.
DetailsGiven that Engineer A had already relayed the defect verbally and lacked both structural expertise and a monitoring mechanism, the board concluded his silence toward other authorities was ethical for now, but only conditionally, because it explicitly tied that permissibility to corrective action occurring 'within a relatively short period of time,' leaving unresolved what should happen if that condition is never confirmed or fails.
DetailsPhase 3: Decision Points
canonical decision point 5
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?
DetailsShould 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?
DetailsShould Engineer A limit his role to flagging the observed defect to qualified parties, or pursue independent investigation and verification despite lacking structural expertise?
DetailsShould 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?
DetailsShould 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?
DetailsPhase 4: Narrative Elements
Characters 4
Timeline Events 21 -- synthesized from Step 3 temporal dynamics
An engineering firm is retained to inspect pavement conditions under a contract that explicitly limits the scope of work to pavement assessment, but during the inspection a defective bridge wall is discovered that falls outside this defined scope. This sets up a tension between the contractual boundaries of the assignment and the engineer's broader professional obligation to address safety concerns encountered in the field.
A client retains a consulting engineering firm specifically to perform a pavement condition inspection, establishing a defined scope of services and the professional relationship that will govern the project. This retention agreement becomes significant later when a structural defect is found outside the agreed scope of work.
The primary consultant brings in a subconsultant to assist with or perform portions of the inspection work, expanding the team involved in the project. This subcontracting arrangement later plays a role in how information about the discovered defect is communicated and handled.
The client requests that the engineer omit the bridge wall defect from the written inspection report, since it falls outside the contracted pavement inspection scope. This request creates an ethical dilemma between honoring the client's wishes regarding contractual scope and the engineer's duty to protect public safety.
Despite the defect being outside the contracted scope of work, the engineer documents the defective bridge wall's condition, creating a record of the safety issue that was observed during the pavement inspection. This documentation demonstrates the engineer's recognition of the defect's seriousness even though it exceeded the assignment's boundaries.
The engineer verbally communicates the safety concern about the defective bridge wall to relevant parties rather than, or in addition to, including it in a formal written report. This choice of informal communication raises questions about whether verbal notice adequately fulfills the engineer's ethical obligation to ensure public safety.
Information about the bridge wall defect is passed along through the project team, likely between the subconsultant and the primary consultant or client, rather than being formally incorporated into the official inspection documentation. This relay of information outside formal reporting channels raises concerns about whether the safety issue receives adequate attention and follow up.
The engineer ultimately complies with the client's request and excludes the bridge wall defect from the final written report, limiting the document to the originally contracted pavement scope. This compliance raises the central ethical question of whether adhering to contractual scope limitations can justify omitting a known safety hazard from formal documentation.
Nonreporting to Authorities
Vehicle Control Loss
Bridge Wall Failure
Officer Fatality
Defect Discovery
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.
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?
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?
Should Engineer A limit his role to flagging the observed defect to qualified parties, or pursue independent investigation and verification despite lacking structural expertise?
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?
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?
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.
Ethical Tensions 3
Decision Moments 5
- Report Verbally, Retain in Field Notes board choice
- Include Defect in Final Written Report
- Limit All Disclosure to Contracted Scope
- Rely on Public Agency to Act board choice
- Independently Report to State Licensing or Safety Board
- Escalate Within the Public Agency Hierarchy
- Flag Observation to Qualified Parties board choice
- Conduct Independent Investigation Beyond Scope
- Withhold Observation Absent Certainty
- Monitor and Escalate if Inaction Persists board choice
- Consider Duty Discharged After Verbal Report
- Request Formal Confirmation from Agency
- Maintain Original Disclosure Without New Escalation board choice
- Immediately Report to Accident Investigators
- Commission Independent Assessment Before Acting