Step 4: Full View

Entities, provisions, decisions, and narrative

Public Health and Safety—Scaffolding for Highway Ramp
Step 4 of 5

365

Entities

3

Provisions

5

Precedents

17

Questions

25

Conclusions

Oscillation

Transformation
Oscillation Duties shift back and forth between parties over time
Engineer A bears the initial design and disclosure obligation; upon supervisor notification, primary action responsibility shifts to OPQ Construction's supervisor; if the supervisor is non-responsive, responsibility cycles back to Engineer A to escalate internally; if internal channels fail, responsibility shifts again — this time to Engineer A to notify the state DOT directly, which then assumes enforcement responsibility. The design-sealing obligation oscillates in parallel: Engineer A holds it conditionally, it can only be discharged once the supervisor formally acknowledges and addresses the hazard, and it returns to Engineer A as a withholding duty if that acknowledgment is not forthcoming. The cycle is driven by each party's response or non-response, not by fixed project phases, but the structural pattern of recurring obligation transfer between Engineer A and successive institutional actors matches the oscillation definition.
Full Entity Graph
Loading...
Context: 0 Normative: 0 Temporal: 0 Synthesis: 0
Filter:
Building graph...
Entity Types
Synthesis Reasoning Flow
Shows how NSPE provisions inform questions and conclusions - the board's reasoning chain

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

Nodes:
Provision (e.g., I.1.) Question: Board = board-explicit, Impl = implicit, Tens = principle tension, Theo = theoretical, CF = counterfactual Conclusion: Board = board-explicit, Resp = question response, Ext = analytical extension, Synth = principle synthesis Entity (hidden by default)
Edges:
informs answered by applies to
Provisions (3)
View Extraction
II.1. Engineers shall hold paramount the safety, health, and welfare of the public.
How this applies in the case (showing 3 of 76)
Obligation
Engineer A Public Welfare Paramount Scaffolding Design Obligation
This obligation directly mirrors the paramount public safety duty stated in II.1.
Action
Notify Supervisor of Hazard
Holding public safety paramount requires Engineer A to report the hazard to the supervisor when a dangerous condition is identified.
State
Engineer A Observed Illegal Commercial Vehicle Use Creating Scaffolding Hazard
Engineer A's paramount duty to public safety is directly triggered by observing illegal commercial vehicles creating a hazard to scaffolding workers and the public.
Obligation (10)
  • Engineer A Public Welfare Paramount Scaffolding Design Obligation
    This obligation directly mirrors the paramount public safety duty stated in II.1.
  • Engineer A Scaffolding Design Commercial Vehicle Clearance Safety Obligation
    Designing scaffolding to account for foreseeable vehicle hazards is a direct expression of holding public safety paramount.
  • Engineer A Scaffolding Design Commercial Vehicle Clearance Safety Present Case
    The present-case obligation to account for commercial vehicle risk in scaffolding design flows directly from the paramount safety duty.
  • Engineer A Non-Acquiescence Supervisor Refusal Scaffolding Safety Escalation
    Refusing to finalize an unsafe design upholds the paramount public safety obligation when supervisors decline to act.
  • Engineer A Graduated Escalation Scaffolding Commercial Vehicle Hazard Present Case
    The graduated escalation obligation is grounded in the duty to hold public safety paramount throughout the project.
  • Engineer A Pre-Construction Scaffolding Hazard Resolution Present Case
    Ensuring corrective action before construction begins directly serves the paramount public safety duty.
  • Engineer A Supervisor Non-Response Scaffolding Safety External Escalation Present Case
    Escalating externally when the supervisor fails to act is required to uphold the paramount public safety obligation.
  • Engineer A Good Faith Safety Concern External Reporting Threshold Assessment
    Assessing whether to escalate externally is tied to the overarching duty to hold public safety paramount.
  • Engineer A BER 00-5 Public Pressure Resistance Bridge Closure
    Maintaining a bridge closure against public pressure directly reflects the duty to hold public safety paramount over other interests.
  • Engineer A BER 00-5 Five-Ton Limit Strict Enforcement Supervisor Escalation
    Pressing for strict weight-limit enforcement after reopening a bridge upholds the paramount public safety duty.
Action (6)
  • Notify Supervisor of Hazard
    Holding public safety paramount requires Engineer A to report the hazard to the supervisor when a dangerous condition is identified.
  • Escalate to DOT and Law Enforcement
    Holding public safety paramount requires escalating the hazard to authorities when internal reporting is insufficient to protect the public.
  • Design Scaffolding Accommodating Commercial Vehicles
    The design must prioritize public safety by ensuring scaffolding can safely accommodate commercial vehicle loads on the highway ramp.
  • Non-Engineer Orders Crutch Pile Installation
    A non-engineer directing structural installation decisions creates a public safety risk that engineers are obligated to address under the paramount safety duty.
  • Bridge Closure Barricades Erected
    Erecting barricades to close the bridge is a direct action to protect public safety from a known structural hazard.
  • Reinstall Permanent Barricades After Removal
    Reinstalling barricades after unauthorized removal is necessary to maintain public safety protections.
State (10)
  • Engineer A Observed Illegal Commercial Vehicle Use Creating Scaffolding Hazard
    Engineer A's paramount duty to public safety is directly triggered by observing illegal commercial vehicles creating a hazard to scaffolding workers and the public.
  • Engineer A Public Safety at Risk. Worker and Public Endangerment from Scaffolding Proximity to Illegal Traffic
    This provision directly governs Engineer A's obligation to prioritize the safety of workers and parkway users endangered by illegal commercial vehicle traffic near scaffolding.
  • Parkway Restricted-Use Enforcement Gap
    The gap between the parkway's legal restriction and actual commercial vehicle use creates a public safety risk that Engineer A must hold paramount.
  • Pre-Design Worksite Hazard Corrective Action Required. Present Case
    Holding safety paramount requires Engineer A to secure corrective action on the illegal traffic hazard before proceeding with scaffolding design and assembly.
  • Graduated Danger Calibration. Present Case vs BER 00-5
    This provision is the basis for calibrating Engineer A's safety obligation across both cases, as it requires paramount concern for public safety in all circumstances.
  • Ethical Dilemma, Engineer Obligation Scope in Public Safety
    This provision defines the core ethical obligation at the heart of the recurring dilemma about how far an engineer must go to protect public safety.
  • Multi-Authority Escalation Obligation. BER 00-5 Bridge
    Engineer A's obligation to hold safety paramount requires escalating to multiple authorities when the condemned bridge was reopened without authorization.
  • Post-Sale Structural Safety Concern. BER 07-10 Barn
    Holding safety paramount extends Engineer A's obligation to address the barn's structural risk even after the property sale.
  • Non-Imminent Structural Collapse Risk. BER 07-10 Barn
    The risk of collapse under severe snow loads represents a public safety concern that Engineer A must hold paramount under this provision.
  • Safety Closure Enforcement Failure. BER 00-5 Barricades
    The destruction of safety barricades directly undermines the paramount safety obligation this provision imposes on Engineer A.
Constraint (12)
  • Engineer A Public Safety Paramount Scaffolding Design Constraint
    II.1 directly creates the foundational obligation to hold public safety paramount that this constraint enforces.
  • Engineer A Incidental Commute Observation Pre-Design Corrective Action Constraint
    II.1 requires Engineer A to act on safety knowledge before finalizing a design that could endanger workers and the public.
  • Engineer A Restricted Parkway Illegal Use Scaffolding Design Parameter Constraint
    II.1 prohibits designing to a legal restriction alone when known safety hazards exist that could harm the public.
  • Engineer A Foreseeable Illegal Commercial Vehicle Use Scaffolding Design Parameter Constraint
    II.1 requires Engineer A to account for foreseeable hazards to protect public safety in the scaffolding design.
  • Engineer A Pre-Design Corrective Action Prerequisite Scaffolding Commercial Vehicle Hazard
    II.1 mandates that safety concerns be resolved before proceeding with a design that poses public danger.
  • Engineer A Public Safety Paramount Non-Subordination Employment Pressure Scaffolding
    II.1 establishes that public safety is paramount and cannot be subordinated to employer pressure.
  • Engineer A Restricted-Use Enforcement Gap Design Reliance Constraint
    II.1 prevents reliance on an unenforced restriction as a safety basis when public welfare is at risk.
  • Engineer A Supervisor Non-Response Scaffolding Design Finalization Prohibition
    II.1 constrains Engineer A from finalizing a design that remains unsafe regardless of supervisor inaction.
  • OPQ Construction Supervisor Commercial Vehicle Hazard Response Constraint
    II.1 underlies the obligation that no party should direct continuation of a design that endangers public safety.
  • Engineer A Graduated Danger Calibration. Parkway Scaffolding vs BER 00-5 Bridge
    II.1 requires safety escalation proportionate to the hazard, grounding the calibration constraint in public welfare.
  • Engineer A BER 00-5 Public Pressure Bridge Closure Non-Subordination Constraint
    II.1 establishes that public safety determinations cannot be subordinated to community or political pressure.
  • Engineer A BER 07-10 Certificate of Occupancy Non-Preclusion Safety Duty Barn
    II.1 requires Engineer A to maintain safety obligations regardless of administrative approvals already issued.
Principle (10)
  • Public Welfare Paramount Invoked By Engineer A Scaffolding Safety
    This provision directly embodies the obligation to hold public safety paramount, which Engineer A must apply to the scaffolding design risk.
  • Construction Safety Awareness Invoked By Engineer A Scaffolding Design
    Holding safety paramount requires Engineer A to account for foreseeable commercial vehicle risks in the scaffolding design.
  • Good Faith Safety Concern Threshold Invoked By Engineer A Commercial Vehicle Observation
    The paramount safety obligation is triggered when Engineer A's professional judgment identifies a credible safety risk from his observations.
  • Non-Acquiescence to Unsafe Client Directives Invoked By Engineer A Scaffolding Safety
    Holding safety paramount means Engineer A cannot finalize a design that ignores a known hazard even if directed to do so.
  • Public Welfare Paramount Invoked In Present Case Scaffolding Safety
    This principle directly restates the paramount safety obligation in the context of the present scaffolding case.
  • Public Welfare Paramount Invoked BER 00-5 Bridge Closure
    Engineer A's bridge closure actions in BER 00-5 exemplify holding public safety paramount against competing pressures.
  • Proportional Escalation Obligation Present Case vs BER 00-5
    The paramount safety obligation applies in both cases but its intensity is calibrated to the degree of imminent risk.
  • Construction Safety Awareness Present Case Commercial Vehicle Hazard
    Recognizing the commercial vehicle hazard to workers on the parkway is a direct application of the paramount safety obligation.
  • Resistance to Public Pressure BER 00-5 Bridge Petition
    Maintaining the bridge closure against public pressure reflects the paramount safety obligation overriding social pressure.
  • Non-Subordination Public Safety BER 00-5 Non-Engineer Override
    The paramount safety obligation means Engineer A cannot subordinate his safety determination to a non-engineer override.
Role (2)
  • Engineer A Construction Scaffolding Design Engineer
    Engineer A must hold paramount the safety of the public when designing scaffolding that poses risks to workers and passing motorists.
  • Engineer A Present Case OPQ Construction Scaffolding Designer
    Engineer A is directly responsible for a scaffolding design that endangers public safety and must prioritize that safety above employer directives.
Event (4)
  • Crutch Piles Installed By Order
    Installing crutch piles under order raises public safety concerns that engineers must hold paramount.
  • Barricades Removed By Unknown Party
    Removal of barricades creates a direct public safety hazard that engineers are obligated to address.
  • Safety Hazard Condition Exists
    An existing safety hazard condition directly implicates the engineer's paramount duty to protect public safety.
  • Bridge Deterioration Discovered
    Discovered bridge deterioration represents a public safety risk that engineers must hold paramount.
Resource (12)
  • NSPE-Code-of-Ethics-Primary
    This provision is the primary normative authority requiring engineers to hold public safety paramount, directly embodied in this resource.
  • OSHA-Construction-Scaffolding-Standard
    Holding public safety paramount requires adherence to minimum scaffolding safety standards established by OSHA for construction environments.
  • FHWA-MUTCD-Work-Zone-Safety
    Holding public safety paramount includes protecting workers from highway traffic hazards addressed by MUTCD work zone safety standards.
  • Construction-Safety-Knowledge-Standard-Instance
    This provision requires Engineer A to apply construction safety knowledge to identify foreseeable risks as part of holding public safety paramount.
  • Constructability-Review-Standard-Instance
    Holding public safety paramount supports conducting a constructability review to identify and mitigate foreseeable safety risks in the scaffolding design.
  • NSPE_Code_of_Ethics
    This provision is a core element of the NSPE Code of Ethics governing Engineer A's obligation to prioritize public safety escalation.
  • BER_Case_00-5
    This case is the primary analogical precedent defining the scope of public safety escalation obligations under the paramount safety duty.
  • BER_Case_07-10
    This case illustrates graduated escalation obligations that flow from the duty to hold public safety paramount.
  • BER_Case_89-7
    This foundational precedent establishes that public health and safety are at the core of engineering ethics under this provision.
  • BER_Case_90-5
    This foundational precedent reinforces that public health and safety issues are central to the paramount safety obligation.
  • BER_Case_92-6
    This foundational precedent supports the principle that holding public safety paramount is a core engineering ethical duty.
  • Engineer_Public_Safety_Escalation_Standard_Resource
    This provision requires the graduated escalation pathway governed by this resource when public safety is at risk.
Capability (10)
  • Engineer A Public Welfare Paramountcy Scaffolding Design
    This capability directly reflects the requirement to hold paramount the safety, health, and welfare of the public in scaffolding design decisions.
  • Engineer A Illegal Vehicle Foreseeable Risk Scaffolding Safety Assessment
    Assessing foreseeable risks to the public from illegal vehicles is a direct expression of holding public safety paramount.
  • Engineer A Scaffolding Clearance Traffic Hazard Integration Design
    Designing scaffolding to account for foreseeable traffic hazards is required by the duty to hold public safety paramount.
  • Engineer A Personal Commute Observation Professional Safety Duty Recognition
    Recognizing that personal observations create a professional safety duty directly ties to the paramount public safety obligation.
  • Engineer A Good Faith Safety Concern External Reporting Threshold Assessment Scaffolding
    Assessing whether observations rise to a reporting threshold is grounded in the overarching duty to protect public safety.
  • Engineer A Imminent vs Non-Imminent Risk Escalation Calibration Scaffolding
    Calibrating escalation urgency based on risk level is a practical application of the duty to protect public welfare.
  • Engineer A Imminent vs Non-Imminent Risk Escalation Calibration Scaffolding Case
    Correctly calibrating the non-imminent risk in the present case reflects the duty to hold public safety paramount proportionally.
  • Engineer A Multi-Precedent Public Safety Duty Synthesis Present Case
    Synthesizing precedent to determine appropriate safety response is rooted in the fundamental duty to protect public welfare.
  • OPQ Construction Supervisor Commercial Vehicle Hazard Response Safety Obligation
    The supervisor's obligation to respond to hazard notifications is grounded in the paramount duty to protect public safety.
  • Engineer A Precedent-Informed Proportional Safety Response Calibration Present Case
    Calibrating a proportional safety response using precedent directly serves the requirement to hold public safety paramount.
II.1.f. Engineers having knowledge of any alleged violation of this Code shall report thereon to appropriate professional bodies and, when relevant, also to public authorities, and cooperate with the proper authorities in furnishing such information or assistance as may be required.
How this applies in the case (showing 3 of 77)
Obligation
Engineer A Incidental Commute Commercial Vehicle Observation Reporting Obligation
Reporting observed illegal vehicle activity to the supervisor aligns with the duty to report known violations to appropriate bodies.
Action
Notify Supervisor of Hazard
Reporting a known safety violation to the supervisor is required under the duty to report alleged violations to appropriate bodies.
State
Engineer A Unverified Concern. Scaffolding Hazard Not Yet Formally Reported
This provision directly applies because Engineer A has knowledge of a safety violation but has not yet formally reported it to appropriate authorities.
Obligation (13)
  • Engineer A Incidental Commute Commercial Vehicle Observation Reporting Obligation
    Reporting observed illegal vehicle activity to the supervisor aligns with the duty to report known violations to appropriate bodies.
  • Engineer A Written Supervisor Notification Commercial Vehicle Hazard
    Written notification to the supervisor of the observed hazard is a direct form of reporting a known violation as required by II.1.f.
  • Engineer A Non-Acquiescence Supervisor Refusal Scaffolding Safety Escalation
    Escalating to external authorities when the supervisor refuses to act corresponds to reporting to public authorities under II.1.f.
  • Engineer A Graduated Escalation Scaffolding Commercial Vehicle Hazard Present Case
    The graduated escalation sequence including external notification mirrors the reporting and cooperation duties in II.1.f.
  • Engineer A DOT Law Enforcement Notification Through Supervisor Present Case
    Ensuring DOT and law enforcement are notified of the commercial vehicle hazard directly fulfills the duty to report to public authorities.
  • Engineer A Supervisor Non-Response Scaffolding Safety External Escalation Present Case
    External escalation after supervisor inaction is the precise scenario addressed by the duty to report to public authorities in II.1.f.
  • Engineer A Incidental Commute Observation Safety Reporting Present Case
    Reporting the personally observed safety hazard to the supervisor is a direct application of the reporting obligation in II.1.f.
  • Engineer A Illegal Traffic Hazard Supervisor Notification Writing Present Case
    Written notification of the observed illegal traffic hazard to the supervisor fulfills the reporting duty specified in II.1.f.
  • Engineer A Good Faith Safety Concern External Reporting Threshold Assessment
    Assessing when to escalate to external authorities is directly tied to determining when II.1.f. reporting obligations are triggered.
  • Engineer A BER 00-5 Full-Bore Multi-Authority Campaign Bridge Collapse
    Contacting multiple authorities about the bridge collapse risk is a direct application of the duty to report to appropriate professional bodies and public authorities.
  • Engineer A BER 07-10 Deadline-Conditioned Escalation County State Building Officials
    Escalating to county and state building officials after a deadline reflects the duty to report to appropriate authorities under II.1.f.
  • Engineer A BER 07-10 Written Notification Town Supervisor Barn Safety
    Written notification to the town supervisor about the barn risk is a form of reporting a known safety violation to an appropriate body.
  • Engineer A BER 00-5 Retired Inspector Unlicensed Practice Determination
    Determining whether the retired inspector engaged in unlicensed practice relates to the duty to report alleged code violations to professional bodies.
Action (3)
  • Notify Supervisor of Hazard
    Reporting a known safety violation to the supervisor is required under the duty to report alleged violations to appropriate bodies.
  • Escalate to DOT and Law Enforcement
    Reporting the hazard and code violations to DOT and law enforcement directly fulfills the obligation to notify public authorities of violations.
  • Non-Engineer Orders Crutch Pile Installation
    A non-engineer directing structural work constitutes an alleged violation that engineers must report to appropriate professional bodies and authorities.
State (9)
  • Engineer A Unverified Concern. Scaffolding Hazard Not Yet Formally Reported
    This provision directly applies because Engineer A has knowledge of a safety violation but has not yet formally reported it to appropriate authorities.
  • Engineer A Observed Illegal Commercial Vehicle Use Creating Scaffolding Hazard
    Engineer A's personal observation of illegal commercial vehicle use constitutes knowledge of a violation that must be reported to appropriate bodies and public authorities.
  • Parkway Restricted-Use Enforcement Gap
    The observed violation of the parkway's legal restriction triggers Engineer A's duty to report to proper authorities and cooperate with them.
  • Pre-Design Worksite Hazard Corrective Action Required. Present Case
    Reporting the illegal traffic violation to appropriate authorities is a necessary step in securing corrective action before scaffolding work proceeds.
  • Multi-Authority Escalation Obligation. BER 00-5 Bridge
    This provision requires Engineer A to report the unauthorized bridge reopening to appropriate professional bodies and public authorities and cooperate with them.
  • Safety Closure Enforcement Failure. BER 00-5 Barricades
    The removal and destruction of safety barricades constitutes a violation that Engineer A must report to appropriate authorities under this provision.
  • Non-Imminent Structural Collapse Risk. BER 07-10 Barn
    Engineer A's knowledge of the barn's structural collapse risk obligates reporting to appropriate authorities even if danger is not imminent.
  • Certificate of Occupancy Issued Despite Structural Concern. BER 07-10
    The town's issuance of a certificate of occupancy despite known structural concerns represents a situation where Engineer A should report to appropriate professional bodies.
  • Ethical Dilemma, Engineer Obligation Scope in Public Safety
    This provision helps define the scope of the reporting obligation that is central to the recurring ethical dilemma engineers face in public safety situations.
Constraint (11)
  • Engineer A Supervisor Non-Response External Escalation Scaffolding Hazard Present Case
    II.1.f directly requires reporting to appropriate authorities when internal escalation fails to address a safety violation.
  • Engineer A Written Supervisor Notification Constraint. Commercial Vehicle Scaffolding Hazard
    II.1.f supports the requirement to document notification formally as a predicate to reporting to proper authorities.
  • Engineer A Good Faith Safety Concern External Reporting Threshold Constraint
    II.1.f defines the scope and conditions under which external reporting is required, directly shaping this constraint.
  • Engineer A Fact Command Pre-Reporting Readiness Constraint. Parkway Scaffolding
    II.1.f requires Engineer A to be prepared with all relevant facts before reporting to authorities.
  • Engineer A Supervisor-Mediated DOT Law Enforcement Notification Parkway Hazard
    II.1.f requires cooperation with and notification of public authorities such as DOT and law enforcement regarding the hazard.
  • Engineer A Graduated Escalation Calibration Present Case vs BER 00-5 vs BER 07-10
    II.1.f grounds the graduated escalation pathway by specifying reporting to professional bodies and public authorities as required steps.
  • Engineer A BER 00-5 Full-Bore Multi-Authority Campaign Constraint Bridge Collapse
    II.1.f directly required the multi-authority escalation campaign to professional bodies and public authorities in BER 00-5.
  • Engineer A BER 00-5 Non-Engineer Authority Bridge Reopening Non-Acquiescence Constraint
    II.1.f obligates Engineer A to report rather than acquiesce when a non-engineer authority overrides a safety determination.
  • Engineer A BER 00-5 Unlicensed Bridge Inspector Practice Reporting Constraint
    II.1.f requires reporting alleged violations of engineering standards, including unlicensed practice, to appropriate bodies.
  • Engineer A BER 07-10 New Owner Priority Written Notification Barn Structural Deficiency
    II.1.f supports the obligation to notify relevant parties in writing of safety concerns as a step toward proper authority reporting.
  • Engineer A BER 07-10 Graduated Deadline-Conditioned Escalation County State Building Officials
    II.1.f directly grounds the escalation to county and state building officials when lower-level notification is unaddressed.
Principle (13)
  • Proactive Risk Disclosure Invoked By Engineer A Commercial Vehicle Hazard
    This provision requires reporting known violations or hazards to appropriate bodies, directly grounding the proactive disclosure obligation.
  • Incidental Observation Disclosure Obligation Invoked By Engineer A Commute Observation
    The provision requires reporting even when the knowledge arises outside the formal scope of engagement, as with Engineer A's commute observation.
  • Written Documentation Requirement Invoked By Engineer A Safety Notification
    Reporting to appropriate authorities implies creating a clear record, supporting the written documentation requirement.
  • Contextual Calibration of Public Safety Reporting Invoked By Engineer A Commercial Vehicle Hazard
    The provision's reporting obligation must be calibrated to the nature and severity of the observed hazard.
  • Proactive Risk Disclosure Present Case Commercial Vehicle Hazard
    This principle directly applies the reporting obligation to the present case's commercial vehicle hazard disclosure to supervisor and authorities.
  • Written Documentation Requirement Present Case Scaffolding Safety
    Written notification to the supervisor creates the unambiguous record needed to satisfy the reporting obligation under this provision.
  • Written Documentation Requirement BER 07-10 Barn Safety
    The BER 07-10 written notification requirement reflects the same obligation to report to appropriate parties in a documented manner.
  • Persistent Escalation BER 07-10 Town Supervisor Follow-Up
    When initial reporting produces no action, this provision supports escalating follow-up to ensure the report reaches effective authorities.
  • Persistent Escalation BER 00-5 Multi-Authority Campaign
    Engineer A's campaign to report to multiple authorities after being overridden directly reflects the obligation to report to appropriate bodies.
  • Third-Party Direct Notification BER 07-10 Jones Barn Owner
    Direct written notification to the barn owner is a form of reporting to a relevant party as required by this provision.
  • Contextual Calibration Public Safety Reporting Present Case vs Prior Cases
    The provision's reporting obligation is explicitly calibrated in the Board's analysis to the lesser imminence of the present case versus prior cases.
  • Public Employee Engineer Heightened Obligation BER 00-5
    A public engineer's heightened reporting obligation is a direct intensification of the duty to report to appropriate authorities under this provision.
  • Unlicensed Practice Challenge Obligation BER 00-5 Bridge Inspector
    Reporting the retired inspector's potentially unlicensed activities to appropriate professional bodies is required by this provision.
Role (3)
  • Engineer A Construction Scaffolding Design Engineer
    Engineer A has knowledge of a safety violation involving commercial vehicles on the parkway and must report it to appropriate authorities.
  • Engineer A Present Case OPQ Construction Scaffolding Designer
    Engineer A is obligated to report the known safety hazard to proper authorities after notifying his supervisor, who has not acted on the concern.
  • OPQ Construction Supervisor Present Case
    The supervisor received Engineer A's safety notification and bears responsibility for reporting or acting on the alleged violation through proper channels.
Event (4)
  • Barricades Removed By Unknown Party
    The removal of safety barricades by an unknown party is an alleged violation that should be reported to appropriate authorities.
  • Safety Hazard Condition Exists
    Knowledge of an existing safety hazard condition obligates the engineer to report it to proper authorities.
  • Commercial Vehicles Observed Illegally
    Observing illegal commercial vehicle activity is a violation that should be reported to appropriate public authorities.
  • Bridge Deterioration Discovered
    Discovery of bridge deterioration is information that must be reported to appropriate professional bodies and public authorities.
Resource (7)
  • NSPE-Code-of-Ethics-Primary
    This provision directly references the obligation to report violations to professional bodies and public authorities, a duty codified in this primary resource.
  • Engineer-Safety-Recommendation-Rejection-Standard-Instance
    If a supervisor rejects safety recommendations, this provision requires Engineer A to report the violation to appropriate authorities.
  • NSPE_Code_of_Ethics
    This provision is part of the NSPE Code of Ethics governing Engineer A's escalation obligations when safety violations are known.
  • BER_Case_00-5
    This case directly addresses the scope of reporting and escalation obligations when a code violation affecting public safety is identified.
  • BER_Case_07-10
    This case illustrates the graduated written notification and reporting duties triggered when initial notifications are insufficient.
  • Engineer_Public_Safety_Escalation_Standard_Resource
    This provision mandates the escalation pathway to supervisors, DOT officials, and law enforcement governed by this resource.
  • Unlicensed_Practice_Reporting_Standard_Resource
    This provision requires reporting alleged violations including unlicensed practice to appropriate professional bodies and public authorities.
Capability (14)
  • Engineer A Supervisor Non-Response Scaffolding Safety External Escalation Present Case
    This capability directly addresses the obligation to report to appropriate authorities when the supervisor fails to act on a known safety violation.
  • Engineer A Supervisor Non-Response Scaffolding Safety External Escalation
    Recognizing the obligation to escalate externally when the supervisor declines to address the hazard directly corresponds to the duty to report violations to proper authorities.
  • Engineer A Multi-Agency Jurisdiction Identification Scaffolding Safety Escalation
    Identifying all appropriate authorities for escalation is required by the duty to report to proper authorities and cooperate with them.
  • Engineer A Written Supervisor Notification Illegal Vehicle Hazard
    Written notification initiates the reporting chain required when a potential code violation or safety hazard is known.
  • Engineer A Good Faith Safety Concern External Reporting Threshold Assessment Scaffolding
    Assessing whether the threshold for external reporting has been met directly relates to the duty to report alleged violations to appropriate bodies.
  • Engineer A Corrective Action Pre-Construction Resolution Identification Present Case
    Identifying corrective action options including external reporting supports the obligation to cooperate with authorities in furnishing information.
  • Engineer A Public vs Private Employee Safety Escalation Distinction Present Case
    Recognizing how employment status affects escalation sequencing is relevant to determining the appropriate authorities to report to under this provision.
  • Engineer A Supervisor-First Escalation Sequencing Present Case
    Sequencing escalation starting with the supervisor before external authorities reflects the structured reporting obligation under this provision.
  • Engineer A Deadline-Conditioned Escalation County State Building Officials BER 07-10
    Conditional escalation to county and state officials is a direct application of the duty to report to appropriate authorities when internal resolution fails.
  • Engineer A Written Notification Town Supervisor Barn Safety BER 07-10
    Written notification to the town supervisor about structural risk reflects the reporting obligation to appropriate parties under this provision.
  • Engineer A New Owner Priority Notification Jones Barn BER 07-10
    Notifying the new owner in writing of structural risk is part of the duty to report known safety concerns to relevant parties.
  • Engineer A Five-Ton Weight Limit Strict Enforcement Supervisor Escalation BER 00-5
    Pressing the supervisor for strict enforcement of safety limits reflects the duty to report and act on known safety violations.
  • Engineer A Non-Engineer Infrastructure Decision Override Recognition BER 00-5
    Recognizing that a non-engineer overrode a professional safety determination triggers the duty to report to appropriate authorities.
  • Engineer A Public Pressure Non-Subordination Bridge Closure BER 00-5
    Maintaining the bridge closure against public pressure reflects the duty to cooperate with proper authorities rather than subordinate safety to external pressure.
III.2.b. 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 47)
Obligation
Engineer A Non-Acquiescence Supervisor Refusal Scaffolding Safety Escalation
Refusing to finalize a non-conforming scaffolding design and escalating externally directly mirrors the duty in III.2.b. to notify authorities and withdraw.
Action
Engineer A Accepts Design Assignment
Engineer A must ensure the accepted design assignment conforms to applicable engineering standards before completing or sealing plans.
State
Engineer A Client Relationship with OPQ Construction and State DOT
This provision governs Engineer A's obligation to notify proper authorities and withdraw from service if OPQ Construction or the DOT insists on proceeding with non-conforming plans.
Obligation (6)
  • Engineer A Non-Acquiescence Supervisor Refusal Scaffolding Safety Escalation
    Refusing to finalize a non-conforming scaffolding design and escalating externally directly mirrors the duty in III.2.b. to notify authorities and withdraw.
  • Engineer A Supervisor Non-Response Scaffolding Safety External Escalation Present Case
    Refusing to complete the scaffolding design and escalating when the supervisor ignores the hazard is the exact conduct required by III.2.b.
  • Engineer A Scaffolding Alternative Design Presentation Supervisor
    Presenting alternative conforming designs before withdrawing reflects the obligation to seek compliant solutions as implied by III.2.b.
  • Engineer A Corrective Options Presentation Supervisor Present Case
    Presenting corrective options to the supervisor before escalating aligns with the process contemplated by III.2.b. prior to withdrawal.
  • Engineer A Graduated Escalation Scaffolding Commercial Vehicle Hazard Present Case
    The graduated escalation culminating in refusal to finalize the design corresponds to the notification and withdrawal sequence in III.2.b.
  • Engineer A BER 07-10 Deadline-Conditioned Escalation County State Building Officials
    Setting a deadline and then escalating to authorities if unresolved reflects the notify-and-escalate structure of III.2.b.
Action (4)
  • Engineer A Accepts Design Assignment
    Engineer A must ensure the accepted design assignment conforms to applicable engineering standards before completing or sealing plans.
  • Supervisor Directs Scaffolding Design
    If the supervisor directs a design not conforming to engineering standards, the engineer must notify proper authorities and withdraw from the project.
  • Design Scaffolding Accommodating Commercial Vehicles
    The scaffolding plans must conform to applicable engineering standards and must not be signed or sealed if they do not meet those standards.
  • Non-Engineer Orders Crutch Pile Installation
    A non-engineer ordering structural installation contrary to engineering standards represents unprofessional conduct requiring notification of proper authorities.
State (6)
  • Engineer A Client Relationship with OPQ Construction and State DOT
    This provision governs Engineer A's obligation to notify proper authorities and withdraw from service if OPQ Construction or the DOT insists on proceeding with non-conforming plans.
  • Pre-Design Worksite Hazard Corrective Action Required. Present Case
    Engineer A must not complete or seal scaffolding plans that do not conform to safety standards given the illegal traffic hazard, and must notify authorities if the client insists on proceeding.
  • Engineer A Observed Illegal Commercial Vehicle Use Creating Scaffolding Hazard
    Designing scaffolding without addressing the illegal commercial vehicle hazard would result in plans not in conformity with applicable engineering safety standards.
  • Non-Engineer Authority Directing Bridge Reopening. BER 00-5
    A non-engineer directing unsafe bridge work represents a situation where Engineer A must refuse to complete non-conforming plans and notify proper authorities.
  • Unlicensed Bridge Inspector Practice. BER 00-5
    Plans or recommendations based on an unlicensed inspector's evaluation would not conform to applicable engineering standards, triggering this provision's obligations.
  • Bridge Closure Public Pressure Override. BER 00-5
    Public pressure to override Engineer A's professional safety closure decision implicates the obligation to refuse non-conforming work and notify proper authorities.
Constraint (9)
  • Engineer A Restricted Parkway Illegal Use Scaffolding Design Parameter Constraint
    III.2.b prohibits signing or completing plans not conforming to applicable engineering standards, directly constraining design to inadequate parameters.
  • Engineer A Foreseeable Illegal Commercial Vehicle Use Scaffolding Design Parameter Constraint
    III.2.b prevents Engineer A from completing a scaffolding design that ignores foreseeable hazards inconsistent with engineering standards.
  • Engineer A Supervisor Non-Response Scaffolding Design Finalization Prohibition
    III.2.b requires withdrawal from further service if the employer insists on proceeding with a non-conforming design after notification.
  • Engineer A Public Safety Paramount Non-Subordination Employment Pressure Scaffolding
    III.2.b directly supports non-subordination to employer pressure by requiring notification of authorities and withdrawal if necessary.
  • Engineer A Scaffolding Alternative Design Presentation Constraint
    III.2.b implies Engineer A must seek conforming design alternatives rather than seal plans that do not meet engineering standards.
  • Engineer A Corrective Action Options Presentation Supervisor Scaffolding Hazard
    III.2.b requires Engineer A to present corrective options to the supervisor before being compelled to notify authorities or withdraw.
  • OPQ Construction Supervisor Commercial Vehicle Hazard Response Constraint
    III.2.b constrains the supervisor from directing Engineer A to proceed with a non-conforming design without addressing the hazard.
  • Engineer A Pre-Design Corrective Action Prerequisite Scaffolding Commercial Vehicle Hazard
    III.2.b prohibits completing plans not in conformity with engineering standards, making corrective action a prerequisite to finalization.
  • Engineer A BER 00-5 Non-Engineer Authority Bridge Reopening Non-Acquiescence Constraint
    III.2.b requires Engineer A not to seal or approve plans directed by a non-engineer that do not conform to engineering standards.
Principle (7)
  • Non-Acquiescence to Unsafe Client Directives Invoked By Engineer A Scaffolding Safety
    This provision directly prohibits completing plans not conforming to engineering standards and requires withdrawal if the client insists, grounding the non-acquiescence obligation.
  • Faithful Agent Obligation Invoked By Engineer A Scaffolding Assignment
    The provision defines the boundary of the faithful agent role by prohibiting sealing nonconforming plans even under client direction.
  • Proactive Design Alternatives Presentation Invoked By Engineer A Scaffolding Hazard Mitigation
    Presenting alternative conforming designs is a constructive way to avoid completing nonconforming plans as prohibited by this provision.
  • Proactive Design Alternatives Presentation Present Case Scaffolding
    Identifying alternative scaffolding approaches helps Engineer A comply with this provision by avoiding nonconforming final plans.
  • Faithful Agent Obligation Present Case OPQ Construction
    Engineer A must execute the assignment diligently but cannot seal plans that violate engineering standards, as this provision requires.
  • Non-Subordination Public Safety BER 00-5 Non-Engineer Override
    Allowing a non-engineer to override a safety determination and implement a substandard solution is analogous to completing nonconforming plans under client pressure.
  • Proportional Escalation Obligation BER 07-10 Measured Response
    The measured escalation in BER 07-10 includes refusing to approve nonconforming work and notifying proper authorities, consistent with this provision.
Role (2)
  • Engineer A Construction Scaffolding Design Engineer
    Engineer A must not sign or seal scaffolding plans that do not conform to applicable engineering standards given the commercial vehicle weight hazard.
  • Engineer A Present Case OPQ Construction Scaffolding Designer
    If OPQ Construction insists on proceeding with noncompliant scaffolding design, Engineer A must notify proper authorities and withdraw from the project.
Event (2)
  • Crutch Piles Installed By Order
    Installing crutch piles by order suggests plans or methods not conforming to engineering standards, triggering the duty to notify authorities or withdraw.
  • Scaffolding Assignment Received
    Accepting the scaffolding assignment creates the obligation to ensure plans conform to applicable engineering standards.
Resource (5)
  • OSHA-Construction-Scaffolding-Standard
    This provision prohibits signing plans not conforming to applicable engineering standards, including OSHA scaffolding safety requirements.
  • FHWA-MUTCD-Work-Zone-Safety
    This provision requires conformity with applicable standards such as MUTCD work zone safety requirements before signing or sealing plans.
  • Engineer-Safety-Recommendation-Rejection-Standard-Instance
    This provision directly applies when a supervisor insists Engineer A proceed without addressing safety concerns, requiring notification and withdrawal.
  • Constructability-Review-Standard-Instance
    This provision supports requiring a constructability review to ensure plans conform to applicable engineering standards before sealing.
  • BER_Case_00-5
    This case provides analogical guidance on the obligation to refuse to complete non-conforming plans and escalate when directed otherwise.
Capability (6)
  • Engineer A Scaffolding Clearance Traffic Hazard Integration Design
    Designing scaffolding that conforms to applicable engineering standards by accounting for foreseeable traffic hazards is directly required by this provision.
  • Engineer A Scaffolding Alternative Configuration Presentation Supervisor
    Presenting alternative conforming scaffolding configurations to the supervisor reflects the duty not to complete plans not in conformity with engineering standards.
  • Engineer A Construction Safety Competence Boundary Self-Recognition Scaffolding
    Recognizing competence boundaries ensures the engineer does not sign or seal plans beyond their expertise, as required by this provision.
  • Engineer A Corrective Action Pre-Construction Resolution Identification Present Case
    Identifying corrective actions before construction begins supports the obligation to ensure plans conform to applicable engineering standards.
  • Engineer A Crutch Pile Remediation Adequacy Collaborative Verification BER 00-5
    Collaboratively verifying remediation adequacy ensures that engineering plans and specifications meet applicable standards before being sealed.
  • Engineer A Unlicensed Bridge Inspector Engineering Practice Determination BER 00-5
    Determining whether unlicensed activities constitute engineering practice relates to ensuring only conforming, properly authorized plans are completed and sealed.
Cross-Case Connections
View Extraction
Explicit Board-Cited Precedents 5 Lineage Graph

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

Principle Established:

When an engineer identifies a serious and imminent public safety threat, the engineer must take immediate and escalating steps to notify supervisors, public officials, law enforcement, and licensing boards until corrective action is taken.

Citation Context:

The Board cited this case as a primary analogy illustrating how engineers must respond to public safety threats, while also distinguishing it from the present case due to differences in imminence and scope of danger.

Relevant Excerpts
discussion: "An illustration of how the Board has addressed this dilemma can be found in BER Case No. 00-5 . There, Engineer A was an engineer with a local government and learned about a critical situation involving a bridge"
discussion: "The facts and circumstances of the present case are somewhat different in several respects than the situation involved in BER Case No. 00-5 . First, the danger involved, while possibly significant, is not nearly as imminent"

Principle Established:

Basic and fundamental issues of public health and safety are at the core of engineering ethics, and engineers must not yield to public pressure or employment pressures when great dangers are present.

Citation Context:

The Board cited this case within the discussion of BER Case No. 00-5 to support the principle that engineers must not bow to public pressure or employment situations when fundamental public health and safety issues are at stake.

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

Principle Established:

When an engineer identifies a potential structural safety concern, the engineer fulfills ethical obligations by notifying the appropriate authority verbally and in writing, following up if no action is taken, and escalating to higher authorities only if the initial notification proves ineffective within a reasonable time.

Citation Context:

The Board cited this case to illustrate a more measured approach to engineer notification obligations where the danger, while real, is less imminent, requiring written notification to supervisors and owners and continued monitoring rather than a full escalation campaign.

Relevant Excerpts
discussion: "More recently, in BER Case No. 07-10 , Engineer A designed and built a barn with horse stalls on his property. Four years later, Engineer A sold the property, including the barn, to Jones."
discussion: "The Board decided that Engineer A had fulfilled his ethical obligation by notifying the town supervisor, but that Engineer A should also notify the new owner in writing of the perceived deficiency."

Principle Established:

Engineers must take immediate steps to contact county governing authorities, prosecutors, state and/or federal transportation/highway officials, and the state engineering licensure board when public safety is at risk, or they ignore their basic professional and ethical obligations.

Citation Context:

The Board cited this case within the discussion of BER Case No. 00-5 to support the principle that engineers must take immediate steps to contact governing authorities and other officials when public safety is endangered.

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

Principle Established:

For an engineer to bow to public pressure or employment situations when the engineer believes there are great dangers present would be an abrogation of the engineer's most fundamental responsibility and obligation.

Citation Context:

The Board cited this case within the discussion of BER Case No. 00-5 to reinforce the principle that engineers cannot abdicate their fundamental responsibility to protect public safety due to employment or public pressure.

Relevant Excerpts
discussion: "Reviewing earlier Board of Ethical Review Case Nos. 89-7, 90-5, and 92-6, the Board noted that the facts and circumstances facing Engineer A 'involved basic and fundamental issues of public health and safety which are at the core of engineering ethics.'"
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 63% Facts Similarity 54% Discussion Similarity 70% Provision Overlap 83% Outcome Alignment 100% Tag Overlap 100%
Shared provisions: I.1, II.1, II.1.a, III.1.b, III.2 Same outcome True View Synthesis
Component Similarity 59% Facts Similarity 42% Discussion Similarity 70% Provision Overlap 71% Outcome Alignment 100% Tag Overlap 43%
Shared provisions: I.1, II.1, II.1.a, III.1.b, III.2 Same outcome True View Synthesis
Component Similarity 62% Facts Similarity 38% Discussion Similarity 56% Provision Overlap 50% Outcome Alignment 100% Tag Overlap 83%
Shared provisions: I.1, II.1, II.1.a, III.1.b Same outcome True View Synthesis
Component Similarity 47% Facts Similarity 25% Discussion Similarity 65% Provision Overlap 71% Outcome Alignment 100% Tag Overlap 80%
Shared provisions: I.1, II.1, II.1.a, III.2, III.2.a Same outcome True View Synthesis
Component Similarity 47% Facts Similarity 36% Discussion Similarity 58% Provision Overlap 86% Outcome Alignment 100% Tag Overlap 38%
Shared provisions: I.1, II.1, II.1.a, III.1.b, III.2, III.2.a Same outcome True View Synthesis
Component Similarity 60% Facts Similarity 47% Discussion Similarity 83% Provision Overlap 46% Outcome Alignment 100% Tag Overlap 57%
Shared provisions: I.1, II.1, II.1.a, III.2, III.2.a Same outcome True View Synthesis
Component Similarity 55% Facts Similarity 48% Discussion Similarity 53% Provision Overlap 57% Outcome Alignment 100% Tag Overlap 50%
Shared provisions: I.1, II.1, II.1.a, III.1.b Same outcome True View Synthesis
Component Similarity 55% Facts Similarity 37% Discussion Similarity 58% Provision Overlap 62% Outcome Alignment 100% Tag Overlap 38%
Shared provisions: I.1, II.1, II.1.a, III.1.b, III.2 Same outcome True View Synthesis
Component Similarity 52% Facts Similarity 46% Discussion Similarity 57% Provision Overlap 43% Outcome Alignment 100% Tag Overlap 83%
Shared provisions: I.1, II.1.a, III.1.b Same outcome True View Synthesis
Component Similarity 55% Facts Similarity 45% Discussion Similarity 66% Provision Overlap 50% Outcome Alignment 100% Tag Overlap 38%
Shared provisions: I.1, II.1, II.1.a, III.1.b Same outcome True View Synthesis
Questions & Conclusions (1 board)
View Extraction
Board Board question 1

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

Board conclusion Engineer A should immediately notify verbally (and in writing if necessary) Engineer A's immediate supervisor at OPQ Construction of the safety hazards to employees (and others) due to commercial vehicles passing by while inspection and repair is being performed on the ramps.
II.1. III.2.b.
Implicit (4)

At what point does Engineer A's incidental personal observation of illegal commercial vehicle use on the parkway - made during his private commute rather than in a professional capacity - become a formal professional duty to act, and does the source of that observation (personal vs. professional) affect the strength or timing of that obligation?

AnalyticalBeyond the Board's finding that Engineer A should notify his supervisor verbally (and in writing if necessary), the source of Engineer A's observation - a personal commute rather than a formal site inspection - does not diminish the professional weight of that observation. The NSPE Code's public safety paramount obligation is not conditioned on the professional context in which a hazard is discovered. A licensed engineer carries professional responsibilities continuously, and knowledge acquired incidentally that bears directly on a project under active design creates an immediate duty to act. The moment Engineer A recognized that his commute observations were materially relevant to the scaffolding assignment he had accepted, the observation ceased to be merely personal and became professionally actionable. Delay in reporting, justified on the grounds that the observation was informal, would itself constitute a breach of the proactive risk disclosure obligation.
AnalyticalIn response to Q101: Engineer A's personal commute observation of illegal commercial vehicle use on the parkway crosses the threshold from private experience to professional duty at the moment it becomes materially relevant to a specific engineering assignment he is actively executing. The source of the observation - personal rather than professional - does not diminish the strength of the obligation. NSPE Code Section II.1 imposes a duty to hold public safety paramount without qualification as to how the engineer acquired the relevant knowledge. A professional engineer cannot compartmentalize safety-critical information simply because it was gathered outside working hours. The moment Engineer A received the scaffolding design assignment, his prior commute observations became professionally actionable data. If anything, the personal and repeated nature of those observations - suggesting a pattern rather than a single incident - strengthens rather than weakens the evidentiary basis for raising the concern. The timing obligation is therefore immediate upon receipt of the design assignment, not contingent on formal verification conducted in a professional capacity.

Should Engineer A refuse to finalize or seal the scaffolding design until the commercial vehicle hazard has been formally acknowledged and addressed by OPQ Construction or the state DOT, and what are the ethical consequences if he proceeds with design completion under supervisor pressure before corrective action is taken?

AnalyticalThe Board's conclusion that Engineer A should notify his supervisor does not fully resolve whether Engineer A may ethically finalize or seal the scaffolding design before the commercial vehicle hazard has been formally acknowledged and addressed. Code provision III.2.b. creates an independent constraint: Engineer A should not complete, sign, or seal plans that are not in conformity with applicable engineering standards. A scaffolding design that does not account for the foreseeable - if illegal - presence of commercial vehicles on the parkway may fail to conform to applicable construction safety standards, including OSHA scaffolding requirements and FHWA work zone safety guidance, which require hazard identification and mitigation as part of the design process. Accordingly, Engineer A's ethical obligation extends beyond notification: he should condition finalization and sealing of the scaffolding design on the supervisor's formal acknowledgment of the hazard and the adoption of corrective measures, whether through physical design modifications, traffic control, or coordination with the state DOT for enforcement. Proceeding to seal the design under supervisor pressure, without resolution of the hazard, would expose Engineer A to both ethical and professional liability.
AnalyticalIn response to Q102: Engineer A faces a genuine ethical tension regarding whether to finalize or seal the scaffolding design before the commercial vehicle hazard is formally acknowledged and addressed. Code Section III.2.b prohibits Engineer A from completing, signing, or sealing plans that are not in conformity with applicable engineering standards. A scaffolding design that does not account for a foreseeable - even if illegal - traffic hazard may fail to meet applicable safety standards under OSHA scaffolding requirements and FHWA work zone safety guidelines. Accordingly, Engineer A should not finalize or seal the design until either the hazard is formally addressed or the design itself incorporates adequate protective measures. If the supervisor pressures Engineer A to proceed without corrective action, Engineer A's obligation under the Non-Acquiescence to Unsafe Client Directives principle requires him to resist that pressure. Proceeding under supervisor pressure without resolution would expose Engineer A to both ethical and potential legal liability, and would constitute a subordination of public safety to employer convenience that the NSPE Code categorically prohibits.

Does Engineer A have an independent obligation to notify the state department of transportation or law enforcement authorities about the pattern of illegal commercial vehicle use on the parkway - separate from and potentially bypassing his supervisor at OPQ Construction - given that the enforcement gap is a systemic condition that predates and extends beyond the specific scaffolding project?

AnalyticalThe Board's recommendation is appropriately calibrated to the present case's lower severity relative to BER 00-5, but it leaves unresolved the question of what Engineer A must do if the supervisor fails to act. The graduated escalation framework established across BER 00-5 and BER 07-10 makes clear that supervisor notification is the first step in a sequenced escalation chain, not the final one. If OPQ Construction's supervisor dismisses or ignores the commercial vehicle hazard, Engineer A's obligations do not terminate. At that point, Engineer A should escalate through channels available within OPQ Construction, and if those channels also fail, should consider direct notification to the state department of transportation - which is the contracting authority and has both the regulatory interest and the enforcement capacity to address illegal commercial vehicle use on the parkway. This escalation path is less aggressive than the full multi-authority campaign warranted in BER 00-5 - where a condemned bridge was physically reopened over an engineer's objection - but it is more than mere deference to a non-responsive supervisor. The proportionality principle does not reduce Engineer A's obligation to zero in the event of supervisor inaction; it calibrates the form and urgency of escalation, not whether escalation occurs at all.
AnalyticalIn response to Q103: Engineer A does have a latent independent obligation to notify the state department of transportation or law enforcement about the pattern of illegal commercial vehicle use, but that obligation is not yet triggered as a first-order duty in the present case. The appropriate sequencing - consistent with the Proportional Escalation Obligation and the Contextual Calibration of Public Safety Reporting principle - is to first notify the supervisor at OPQ Construction, who as the contractor for the state DOT is positioned to route the concern to the appropriate enforcement authority. The systemic nature of the enforcement gap does not automatically require Engineer A to bypass his employer and contact DOT or law enforcement directly. However, if the supervisor fails to act, or if the supervisor's response is inadequate given the ongoing risk to workers and the public, Engineer A's obligation escalates to include direct notification to the DOT or relevant law enforcement authority. This graduated approach distinguishes the present case from BER 00-5, where the non-engineer public works director's active override of a safety closure decision immediately elevated the escalation obligation to multi-authority reporting.

Is Engineer A ethically obligated to proactively present alternative scaffolding designs - such as configurations with greater clearance buffers, physical barriers, or traffic control measures - as part of his initial notification to his supervisor, rather than simply flagging the hazard and awaiting direction?

AnalyticalThe Board's conclusion focuses on notification but does not address whether Engineer A is obligated to present affirmative design alternatives as part of that notification. The principle of proactive design alternatives presentation - supported by the constructability review standard and OSHA scaffolding requirements - suggests that a competent engineer does not merely flag a hazard and await direction, but arrives at the supervisor conversation with a preliminary assessment of mitigation options. These might include scaffolding configurations with greater lateral clearance buffers, physical barrier integration, phased work scheduling to minimize simultaneous exposure to traffic, or a formal request to the state DOT for temporary enforcement or traffic control during the inspection period. Presenting these options serves two ethical functions: it demonstrates that Engineer A has exercised professional judgment rather than simply transferred the problem upward, and it reduces the likelihood that the supervisor will dismiss the concern as impractical or unactionable. Failure to present alternatives does not negate the notification obligation, but it represents a missed opportunity to fulfill the full scope of Engineer A's professional duty as a design engineer responsible for worker and public safety.
AnalyticalIn response to Q104: Engineer A is ethically well-advised - though not categorically obligated - to present alternative scaffolding configurations or protective measures as part of his initial notification to the supervisor. The Proactive Design Alternatives Presentation principle supports this approach because it transforms Engineer A's notification from a passive hazard flag into a constructive professional contribution, reducing the likelihood that the supervisor will dismiss the concern as speculative or impractical. Presenting options such as increased clearance buffers, physical barriers, or traffic control measures also demonstrates that Engineer A has applied engineering judgment to the problem rather than merely identifying it. However, the ethical floor established by the Board's conclusion requires at minimum that Engineer A notify the supervisor of the hazard verbally and in writing. Presenting design alternatives is a best practice that strengthens the notification and reflects the competence expected of a professional engineer, but the absence of such alternatives does not itself constitute an ethical violation provided the hazard notification is timely and clear.
Cross-cutting analytical questions (12)

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

Principle tension (4)

Does the Faithful Agent Obligation to OPQ Construction - which requires Engineer A to follow his supervisor's direction to design the scaffolding as assigned - conflict with the Public Welfare Paramount principle, which may require Engineer A to withhold or condition his design work until the illegal commercial vehicle hazard is formally resolved, even if doing so delays the project or defies supervisor expectations?

AnalyticalIn response to Q201: The Faithful Agent Obligation to OPQ Construction does not legitimately conflict with the Public Welfare Paramount principle in this case because the NSPE Code establishes an explicit hierarchy in which public safety supersedes employer loyalty. Engineer A's duty to follow his supervisor's direction to design the scaffolding as assigned is a qualified duty, not an absolute one. It is qualified by the condition that the assignment can be executed in conformity with applicable safety standards. Where the assignment as currently scoped cannot be safely executed - because the commercial vehicle hazard has not been addressed - the Faithful Agent Obligation does not require Engineer A to proceed. Rather, it requires Engineer A to serve OPQ Construction's legitimate long-term interests, which include avoiding liability for worker injuries and regulatory violations. Properly understood, notifying the supervisor and conditioning design finalization on hazard resolution is itself an act of faithful agency, not a defiance of it. The apparent conflict dissolves when the Faithful Agent Obligation is correctly interpreted as bounded by professional and ethical constraints.
AnalyticalThe tension between the Faithful Agent Obligation and the Public Welfare Paramount principle was resolved in this case by establishing a clear hierarchical ordering: Engineer A's duty to OPQ Construction does not extend to suppressing, delaying, or softening a safety notification that bears on worker and public welfare. The NSPE Code's structure treats employer loyalty as a derivative obligation - one that operates within the space left open after public safety requirements are satisfied - rather than as a competing obligation of equal weight. Accordingly, the Board's conclusion that Engineer A must notify his supervisor immediately is not a compromise between these two principles but rather an application of the Code's built-in priority rule: faithful agency is owed to OPQ Construction only insofar as it does not require Engineer A to place any interest above public safety. The practical resolution is that Engineer A discharges both obligations simultaneously - he notifies his supervisor (satisfying the faithful agent duty by routing the concern through the proper employment channel) while ensuring the safety concern is formally raised (satisfying the public welfare paramount duty). The two principles conflict only if the supervisor refuses to act, at which point the faithful agent obligation yields entirely.

Does the Good Faith Safety Concern Threshold principle - which requires a reasonable evidentiary basis before triggering formal reporting - conflict with the Proactive Risk Disclosure principle, which arguably demands that Engineer A act on his personal observations of illegal commercial vehicle use without waiting to formally verify frequency, vehicle dimensions, or proximity to the proposed scaffolding footprint?

AnalyticalIn response to Q202: The Good Faith Safety Concern Threshold principle and the Proactive Risk Disclosure principle are not in genuine conflict in this case because Engineer A's repeated personal observations of commercial vehicles on the parkway already satisfy the evidentiary threshold for a good faith safety concern. The Good Faith Safety Concern Threshold does not require formal verification through instrumented measurement, official documentation, or third-party corroboration before a concern may be raised. It requires only that the concern be grounded in a reasonable, non-speculative basis. Repeated firsthand observation of a pattern of illegal vehicle use on the specific roadway where scaffolding will be erected meets that standard. Engineer A is not required to wait for formal verification before notifying his supervisor. Waiting to compile a formal log of dates, times, and vehicle types before raising the concern would itself constitute a breach of the Proactive Risk Disclosure obligation, particularly given that the scaffolding design work is already underway.
AnalyticalThe interaction between the Good Faith Safety Concern Threshold principle and the Proactive Risk Disclosure principle reveals that this case does not require Engineer A to choose between them - rather, the two principles operate in sequence. The Good Faith Safety Concern Threshold sets the minimum evidentiary bar that must be crossed before a professional obligation to report is triggered; repeated personal observation of commercial vehicles illegally using the parkway during Engineer A's own commute clears that bar without requiring formal documentation, vehicle counts, or engineering measurement. Once that threshold is crossed, the Proactive Risk Disclosure principle takes over and demands timely action. The case therefore teaches that the threshold principle functions as a filter against frivolous or speculative reporting, not as a license to delay reporting while gathering additional evidence once a reasonable basis for concern already exists. The Incidental Observation Disclosure Obligation reinforces this reading: the source of Engineer A's knowledge - personal commute rather than formal site inspection - does not diminish the professional duty to act once the observation is sufficient to put a reasonable engineer on notice of a foreseeable hazard. Delay in the name of further verification would itself become an ethical breach under the Proactive Risk Disclosure principle.

Does the Proportional Escalation Obligation - which calibrates Engineer A's response in the present case as less aggressive than the full-bore multi-authority campaign warranted in BER 00-5 - conflict with the Public Welfare Paramount principle, which does not admit of proportionality and demands that any credible threat to worker or public safety be treated with maximum urgency regardless of comparative severity?

AnalyticalIn response to Q203: The Proportional Escalation Obligation does not conflict with the Public Welfare Paramount principle in a way that undermines either. The Public Welfare Paramount principle establishes the goal - protection of worker and public safety - while the Proportional Escalation Obligation governs the means by which that goal is pursued in proportion to the severity and imminence of the threat. In the present case, the hazard is real but less imminent and less certain than the condemned bridge in BER 00-5, where structural collapse was a near-certain consequence of continued use. Proportionality does not mean that Engineer A may treat the scaffolding hazard as unimportant; it means that the initial response - supervisor notification - is calibrated to the severity level, with escalation reserved for cases where the supervisor fails to act. The Public Welfare Paramount principle is fully satisfied by a proportional response that is timely, documented, and followed by escalation if necessary. The two principles are complementary rather than conflicting when correctly applied.
AnalyticalThe interaction between the Proportional Escalation Obligation and the Public Welfare Paramount principle reveals a nuanced but important doctrinal point: proportionality governs the form and sequence of Engineer A's response, not the threshold question of whether to respond at all. Public Welfare Paramount is unconditional in requiring that Engineer A act; Proportional Escalation Obligation determines how aggressively and through how many channels Engineer A must act given the comparative severity of the hazard. In the present case, the Board calibrated Engineer A's obligation as less intensive than the full multi-authority campaign required in BER 00-5 - where a condemned bridge had been unlawfully reopened under non-engineer authority - because the parkway scaffolding hazard, while real and foreseeable, is less certain and less imminent than structural bridge collapse. This calibration does not mean Engineer A may treat the hazard as optional to report; it means that supervisor notification is the appropriate first and currently sufficient step, with external escalation to the state DOT or law enforcement reserved for the contingency of supervisor non-response. The Written Documentation Requirement reinforces rather than conflicts with this calibration: requiring written notification ensures that the proportional response is memorialized and creates an evidentiary record that supports further escalation if needed, making documentation the procedural bridge between the two principles rather than a point of conflict between them.

Does the Written Documentation Requirement - which obligates Engineer A to memorialize his safety notification to his supervisor in writing - conflict with the Contextual Calibration of Public Safety Reporting principle, which might suggest that a verbal notification is sufficient given the relatively lower severity of the present case compared to BER 00-5, and if so, which principle should govern the form and timing of Engineer A's communication?

AnalyticalThe Board's recommendation that Engineer A notify in writing 'if necessary' understates the independent value of written documentation as an ethical safeguard. The written documentation requirement is not merely a contingency for supervisor resistance - it serves as a contemporaneous record that Engineer A fulfilled his professional duty, protects Engineer A from subsequent claims that the hazard was never raised, and creates an institutional record that may prompt OPQ Construction or the state DOT to act even if the immediate supervisor does not. Across BER 00-5 and BER 07-10, written notification was treated as a core component of the escalation obligation, not an optional supplement. In the present case, given that the hazard involves foreseeable risk of worker fatalities and public casualties - even if the probability of any single incident is uncertain - the written documentation requirement should be treated as co-equal with the verbal notification rather than subordinate to it. Engineer A should provide written notification contemporaneously with or immediately following the verbal notification, without waiting to assess whether the supervisor's verbal response is adequate.
AnalyticalIn response to Q204: The Written Documentation Requirement and the Contextual Calibration of Public Safety Reporting principle do not genuinely conflict because the Board's own conclusion resolves the tension by specifying that Engineer A should notify verbally and in writing if necessary. The phrase 'if necessary' introduces a contextual judgment, but in practice the Written Documentation Requirement should be treated as a near-categorical obligation in any professional safety notification context. Written documentation protects Engineer A from later disputes about whether the concern was raised, creates an evidentiary record if escalation becomes necessary, and signals to the supervisor the seriousness with which Engineer A regards the hazard. The relatively lower severity of the present case compared to BER 00-5 may affect the urgency and scope of escalation, but it does not justify omitting written documentation of the initial notification. The Written Documentation Requirement should govern the form of communication; contextual calibration governs the scope and aggressiveness of subsequent escalation steps.
Theoretical (4)

From a deontological perspective, does Engineer A's duty to hold public safety paramount under NSPE Code Section II.1 create an unconditional obligation to report the commercial vehicle hazard regardless of whether the supervisor acts, or is that duty contingent on the severity of the foreseeable harm?

AnalyticalIn response to Q301: From a deontological perspective, Engineer A's duty under NSPE Code Section II.1 to hold public safety paramount is not unconditional in the sense of requiring identical responses regardless of severity, but it is unconditional in the sense that it cannot be waived, overridden by employer pressure, or deferred indefinitely. The duty to act is triggered by the existence of a credible, foreseeable safety risk - not by a threshold of certainty about harm. The severity of the foreseeable harm affects the form and urgency of the required response, not whether a response is required at all. A deontological reading of Section II.1 therefore supports the conclusion that Engineer A must notify his supervisor regardless of the probability of a collision, because the duty is grounded in the nature of the risk (foreseeable harm to workers and the public) rather than in a utilitarian calculation of expected harm. The duty is categorical in its applicability but proportional in its prescribed response.

From a consequentialist perspective, does the relatively low probability that an illegally operating commercial vehicle will actually strike the scaffolding during the inspection window reduce Engineer A's ethical obligation to escalate, or does the magnitude of potential harm - worker fatalities and public casualties - override probability considerations entirely?

AnalyticalIn response to Q302: From a consequentialist perspective, the relatively low probability that an illegally operating commercial vehicle will strike the scaffolding during the inspection window does not reduce Engineer A's ethical obligation to escalate, because the magnitude of potential harm - worker fatalities and public casualties - is sufficiently severe that even a low-probability risk produces an unacceptably high expected harm when multiplied across the duration of the project and the number of workers exposed. Consequentialist analysis also requires consideration of the low cost of the required action: notifying a supervisor is a minimal burden compared to the potential harm avoided. Furthermore, the systemic nature of the enforcement gap - commercial vehicles regularly using the parkway in violation of restrictions - means the probability is not negligible. A consequentialist calculus that discounts the obligation based on low probability alone would be methodologically incomplete and would fail to account for the asymmetry between the cost of notification and the magnitude of potential harm.

From a virtue ethics perspective, does Engineer A demonstrate the professional integrity expected of a competent engineer by treating a personal commute observation as a professionally actionable safety datum, or would a virtuous engineer require more formal verification before raising the concern with a supervisor?

AnalyticalIn response to Q303: From a virtue ethics perspective, a professionally virtuous engineer would treat repeated personal commute observations of illegal commercial vehicle use as professionally actionable safety data without requiring formal verification. The virtue of practical wisdom - phronesis - requires the engineer to recognize when incidental knowledge becomes professionally relevant and to act on that recognition with appropriate judgment. Requiring formal verification before raising a concern with a supervisor would reflect an excess of caution that prioritizes procedural comfort over substantive responsibility. A virtuous engineer is characterized not only by technical competence but by moral attentiveness - the disposition to notice ethically relevant features of one's professional situation and respond to them appropriately. Engineer A's commute observations, repeated over time, constitute exactly the kind of pattern that a morally attentive engineer would recognize as relevant to an active design assignment. Treating those observations as professionally irrelevant because they were made outside working hours would reflect a failure of professional integrity rather than appropriate epistemic caution.

From a deontological perspective, does Engineer A's role as a faithful agent of OPQ Construction create a competing duty that could justify delaying or softening the safety notification to the supervisor, or does the NSPE Code's hierarchy of obligations categorically subordinate employer loyalty to public safety?

AnalyticalIn response to Q304: From a deontological perspective, Engineer A's role as a faithful agent of OPQ Construction does not create a competing duty that could justify delaying or softening the safety notification to the supervisor. The NSPE Code's hierarchy of obligations is explicit: public safety is paramount, and duties to employers are subordinate to that paramount obligation. A deontological reading of the Code treats this hierarchy as categorical rather than as a factor to be weighed against employer loyalty in a balancing test. Moreover, the duty of faithful agency is itself a professional duty, not merely a contractual one, and professional duties are bounded by the ethical framework within which the profession operates. An engineer who softens or delays a safety notification to avoid discomforting a supervisor is not acting as a faithful professional agent - he is acting as a compliant employee, which is a categorically different and ethically inferior role. The faithful agent obligation, properly understood within the NSPE Code framework, requires Engineer A to serve OPQ Construction's legitimate interests, which do not include suppressing safety concerns.
Counterfactual (4)

If Engineer A had formally verified the illegal commercial vehicle use - for example, by documenting dates, times, and vehicle types during commutes - before notifying the supervisor, would that additional evidentiary preparation have strengthened the ethical case for escalation, or would the delay itself constitute a breach of the proactive risk disclosure obligation?

AnalyticalIn response to Q401: If Engineer A had formally verified the illegal commercial vehicle use before notifying the supervisor - by documenting dates, times, and vehicle types during commutes - that additional evidentiary preparation would have strengthened the persuasive force of the notification but would not have been ethically required, and any significant delay incurred in gathering that documentation would itself constitute a breach of the Proactive Risk Disclosure obligation. The Good Faith Safety Concern Threshold requires only a reasonable, non-speculative basis for the concern, which Engineer A's repeated personal observations already provide. Formal documentation is valuable as a supplement to notification, not as a prerequisite for it. An engineer who delays raising a safety concern while compiling a comprehensive evidentiary record - particularly while the design work proceeds - has effectively prioritized procedural thoroughness over the timely protection of worker and public safety. The ethical obligation is to notify promptly on the basis of a good faith concern and to supplement that notification with documentation as it becomes available.

If Engineer A's supervisor had immediately dismissed the commercial vehicle hazard concern and ordered the scaffolding design to proceed without modification, would Engineer A's ethical obligations at that point mirror those of Engineer A in BER 00-5 - requiring a full multi-authority escalation campaign - or would the less imminent and less certain nature of the parkway hazard justify a more measured response?

AnalyticalIn response to Q402: If Engineer A's supervisor had immediately dismissed the commercial vehicle hazard concern and ordered the scaffolding design to proceed without modification, Engineer A's ethical obligations would escalate significantly but would not necessarily mirror the full multi-authority campaign required in BER 00-5. The key distinction is that in BER 00-5, the non-engineer public works director actively overrode a formal safety closure decision, authorized unlicensed engineering practice, and exposed the public to near-certain structural collapse - a combination of factors that justified an aggressive, multi-authority escalation campaign. In the present case, supervisor dismissal of the concern would trigger an obligation to escalate to higher authority within OPQ Construction and, if that fails, to notify the state DOT directly, given that the DOT is the ultimate client and has a direct interest in worker and public safety on its infrastructure. Engineer A would also be obligated to refuse to seal or finalize the scaffolding design until the hazard is addressed. The escalation would be serious and potentially multi-step, but calibrated to the less certain and less imminent nature of the parkway hazard relative to the condemned bridge scenario.

If Engineer A had instead designed the scaffolding to physically accommodate commercial vehicle clearances without notifying the supervisor of the underlying illegal traffic problem, would that design accommodation satisfy Engineer A's ethical obligations, or would it constitute an implicit endorsement of an ongoing legal violation and leave the root enforcement gap unaddressed?

AnalyticalIn response to Q403: If Engineer A had designed the scaffolding to physically accommodate commercial vehicle clearances without notifying the supervisor of the underlying illegal traffic problem, that design accommodation would not satisfy Engineer A's ethical obligations and would constitute a significant ethical failure on multiple grounds. First, it would leave the root enforcement gap entirely unaddressed, meaning that other workers, contractors, and members of the public on the parkway would remain exposed to the hazard from illegal commercial vehicle use beyond the specific scaffolding footprint. Second, it would represent an implicit professional endorsement of a condition that Engineer A knows to be both illegal and dangerous, which is inconsistent with the NSPE Code's requirement that engineers hold public safety paramount. Third, it would deprive OPQ Construction and the state DOT of information they need to make informed decisions about enforcement, traffic control, and project safety planning. A design accommodation that silently absorbs a known hazard without disclosure is not a substitute for the transparency and proactive risk disclosure that the Code requires. It would satisfy the narrow technical requirement of producing a structurally adequate design while failing the broader professional obligation to protect public safety through disclosure.

If the state department of transportation - rather than OPQ Construction - had been Engineer A's direct employer, as was the case for Engineer A in BER 00-5, would Engineer A's heightened public-employee obligation have required direct notification to law enforcement or DOT traffic enforcement authorities without first routing the concern through a private-sector supervisor?

AnalyticalIn response to Q404: If the state department of transportation - rather than OPQ Construction - had been Engineer A's direct employer, as was the case for Engineer A in BER 00-5, Engineer A's heightened public-employee obligation would have materially altered the escalation pathway but not necessarily required bypassing supervisory channels entirely in the first instance. However, as a public employee with direct accountability to the public interest, Engineer A would have had a stronger and more immediate basis for notifying DOT traffic enforcement authorities or law enforcement directly, particularly given that the illegal commercial vehicle use is a systemic enforcement failure within the DOT's own jurisdiction. The public employee context eliminates the private-sector intermediary layer represented by OPQ Construction and places Engineer A in a direct relationship with the public agency responsible for both the infrastructure and its enforcement. This is consistent with the heightened obligation recognized in BER 00-5, where Engineer A's status as a local government engineer informed the Board's expectation of a more aggressive escalation response. In the present case, Engineer A's private-sector employment through OPQ Construction appropriately channels the initial notification through the supervisor, but the public-employee scenario would compress that sequencing and strengthen the case for direct DOT or law enforcement notification.
Decisions & Arguments (9)
View Extraction

When Engineer A's personal commute observations of illegal commercial vehicle use on the parkway become materially relevant to an active scaffolding design assignment, what form and timing of reporting does his professional obligation require?

Options considered:
O1 Immediately notify the supervisor verbally of the commercial vehicle hazard and follow up with written documentation contemporaneously, treating the commute observations as sufficient good-faith basis for reporting without awaiting formal verification Board's choice
O2 Notify the supervisor verbally of the commercial vehicle concern as an informal observation, deferring written documentation unless the supervisor requests it or fails to respond, on the basis that the lower severity of this case relative to BER 00-5 supports contextually calibrated communication
O3 Systematically document dates, times, and vehicle types during subsequent commutes to establish a formal evidentiary record before raising the concern with the supervisor, so that the notification is grounded in verifiable data rather than informal personal impression
Argument structure:
Warrants

The Public Welfare Paramount principle (NSPE Code Section II.1) imposes a duty to hold public safety paramount without qualification as to how the engineer acquired the relevant knowledge. The Incidental Observation Disclosure Obligation establishes that personal commute observations become professionally actionable the moment they are recognized as materially relevant to an active design assignment. The Proactive Risk Disclosure principle demands timely action once a good faith safety concern threshold is crossed. The Written Documentation Requirement establishes that verbal notification should be memorialized in writing as a near-categorical obligation in professional safety notification contexts. Competing against these is the Good Faith Safety Concern Threshold, which might be read to require more formal verification before triggering reporting, and the Contextual Calibration principle, which might suggest that informal verbal notice is sufficient given the lower severity of this case relative to BER 00-5.

Rebuttals

Uncertainty arises from the absence of a clear NSPE or BER rule specifying when off-duty observations become on-duty obligations. The observation is of third-party illegal conduct rather than a design defect, and Engineer A has not formally documented dates, times, or vehicle types. A reasonable engineer might argue that informal personal observations require some threshold of corroboration before they constitute a professional duty to report, and that raising an undocumented concern could be dismissed as speculative. Additionally, the contextual calibration principle might support treating verbal notification as sufficient without contemporaneous written documentation given the hazard's lower severity relative to BER 00-5.

Grounds

Engineer A has accepted a scaffolding design assignment for a noncommercial parkway cloverleaf ramp. Through repeated personal commute experience on the same parkway, Engineer A has observed commercial vehicles illegally traversing the restricted roadway. Engineer A recognizes that these vehicles could endanger construction workers and the public if they pass the proposed scaffolding during inspection and repair operations.

Incidental Commute Observation Safety Reporting Obligation

Before finalizing and sealing the scaffolding design, what must Engineer A do to satisfy his ethical obligation to account for the foreseeable risk from illegally operating commercial vehicles, and does that obligation require presenting affirmative design alternatives alongside the hazard notification?

Options considered:
O1 Notify the supervisor of the hazard with a preliminary presentation of mitigation alternatives: such as increased lateral clearance buffers, physical barrier integration, phased work scheduling, or a formal request to the state DOT for temporary traffic control, and condition finalization and sealing of the design on the supervisor's formal acknowledgment and adoption of corrective measures Board's choice
O2 Redesign the scaffolding to physically accommodate commercial vehicle clearances, incorporating sufficient setback, height clearance, and protective barriers, and proceed to finalize and seal the design on that basis, treating the design accommodation as a complete technical resolution of the foreseeable hazard without requiring a separate supervisor notification of the underlying illegal traffic pattern
O3 Notify the supervisor of the commercial vehicle hazard verbally and in writing, flag the concern as requiring resolution before design finalization, and then proceed to complete the scaffolding design to the supervisor's direction while documenting that the hazard notification was made and that the supervisor accepted responsibility for the corrective action decision
Argument structure:
Warrants

The Scaffolding Design Commercial Vehicle Clearance Safety Obligation requires Engineer A to design scaffolding with sufficient clearance, setback, or protective features to account for the foreseeable risk of prohibited vehicle types, or to formally recommend design alternatives that mitigate the risk. Code Section III.2.b prohibits Engineer A from completing, signing, or sealing plans not in conformity with applicable engineering standards, including OSHA scaffolding requirements and FHWA work zone safety guidance. The Non-Acquiescence to Unsafe Client Directives principle requires Engineer A to resist supervisor pressure to proceed without corrective action. The Proactive Design Alternatives Presentation principle supports presenting mitigation options: such as increased clearance buffers, physical barriers, phased scheduling, or traffic control requests, as part of the initial notification rather than merely flagging the hazard. Competing against these is the Faithful Agent Obligation, which requires Engineer A to follow his supervisor's direction to design the scaffolding as assigned, and the possibility that a design accommodation for commercial vehicle clearances could itself resolve the safety concern without requiring prior enforcement action.

Rebuttals

Uncertainty arises from the possibility that the scaffolding design can be engineered to safely accommodate the foreseeable illegal traffic, through clearance buffers or physical barriers, without requiring prior enforcement action, which would dissolve the need to condition design finalization on external corrective measures. There is also ambiguity in NSPE Code provisions about whether proactive risk disclosure includes solution-generation or only hazard identification, and about whether presenting design alternatives is a categorical obligation or a best practice. A reasonable engineer might argue that flagging the hazard to the supervisor and awaiting direction is a sufficient discharge of the notification obligation, particularly where the supervisor retains decision-making authority over project scope and budget.

Grounds

Engineer A has been directed by his supervisor to design inspection and construction scaffolding for a noncommercial parkway cloverleaf ramp with limited height and width clearance. Engineer A has observed commercial vehicles illegally traversing the parkway and is concerned that such vehicles could endanger construction workers and the public if they pass the proposed scaffolding. The supervisor has been notified of the hazard. The scaffolding design has not yet been finalized or sealed.

Scaffolding Design Commercial Vehicle Clearance Safety Obligation

If Engineer A's supervisor declines to address the commercial vehicle hazard after notification, what escalation steps does Engineer A's professional obligation require, and how should the scope and urgency of that escalation be calibrated relative to the full multi-authority campaign warranted in BER 00-5?

Options considered:
O1 Refuse to finalize or seal the scaffolding design, escalate the hazard concern to higher authority within OPQ Construction, and if internal escalation also fails, notify the state DOT directly as the contracting authority with regulatory interest and enforcement capacity over the parkway, calibrating the escalation as a serious but measured multi-step response rather than an immediate full multi-authority campaign Board's choice
O2 Treat the supervisor's non-response as a decision by the responsible party within OPQ Construction, document that the hazard notification was made and declined, and proceed to finalize the scaffolding design with whatever protective features are technically feasible within the assigned scope, on the basis that the proportional escalation framework does not require external notification for a hazard of this severity and imminence
O3 Simultaneously notify the state DOT and relevant law enforcement authorities directly upon supervisor non-response, without first exhausting internal OPQ Construction escalation channels, on the basis that the systemic and pre-existing nature of the enforcement gap makes this a public-safety condition extending beyond the specific project, warranting the same multi-authority escalation response applied in BER 00-5
Argument structure:
Warrants

The Supervisor Non-Response Scaffolding Safety External Escalation Obligation requires Engineer A to refuse to finalize the scaffolding design without adequate safety measures and, if necessary, to escalate to appropriate external authorities including the state DOT and relevant regulatory bodies. The Graduated Escalation Framework establishes that supervisor notification is the first step in a sequenced chain, not the final obligation. The Persistent Escalation Obligation requires engineers whose initial safety report is unacknowledged to continue pursuing resolution rather than treating an unanswered report as a discharged duty. The Proportional Escalation Obligation calibrates the scope and urgency of escalation to the nature of the risk, the parkway hazard is real and foreseeable but less certain and less imminent than the condemned bridge in BER 00-5, justifying a measured but still serious multi-step response rather than an immediate full multi-authority campaign. The Supervisor-Mediated DOT and Law Enforcement Notification Constraint establishes that direct external notification is appropriate only after the supervisor has failed to act, respecting the institutional chain of responsibility while ensuring corrective action before design finalization.

Rebuttals

Uncertainty arises from the difficulty of distinguishing a project-specific hazard, where employer mediation is appropriate, from a systemic public-safety condition, where the engineer's obligation to the public may require bypassing the employer entirely. The Graduated Danger Calibration between the present case and BER 00-5 may be insufficient to distinguish the two scenarios at the point of supervisor dismissal, because if the scaffolding hazard is determined to present a sufficiently severe risk, the distinction in imminence may not justify a materially different escalation response. There is also uncertainty about what constitutes a reasonable time for the supervisor to act before external escalation is triggered, and whether escalation to higher OPQ Construction authority is a required intermediate step or whether direct DOT notification is permissible upon supervisor non-response.

Grounds

Engineer A has notified his supervisor at OPQ Construction of the foreseeable safety hazard arising from illegal commercial vehicle use on the parkway adjacent to the proposed scaffolding. The supervisor has declined to address the hazard. The scaffolding design has not yet been finalized. The state DOT is the ultimate contracting authority for the project and has both regulatory interest and enforcement capacity over the parkway. The commercial vehicle enforcement gap is systemic and predates the specific scaffolding project.

Supervisor Non-Response Scaffolding Safety External Escalation Obligation Supervisor-Mediated DOT and Law Enforcement Notification Constraint

When Engineer A recognizes that his personal commute observations of illegal commercial vehicle use on the parkway are directly relevant to the scaffolding design assignment he has accepted, what action must he take, and may he finalize or seal the design before the hazard is formally acknowledged and addressed?

Options considered:
O1 Immediately notify the supervisor verbally and in writing of the commercial vehicle hazard, present preliminary mitigation alternatives (increased clearance buffers, physical barriers, traffic control measures), and withhold finalization and sealing of the scaffolding design until the supervisor formally acknowledges the hazard and adopts corrective measures Board's choice
O2 Notify the supervisor verbally of the observed hazard as a preliminary concern, proceed with designing the scaffolding to physically accommodate commercial vehicle clearances as a built-in engineering margin, and treat the design accommodation itself as sufficient mitigation without conditioning design finalization on a formal supervisor response
O3 Document the commute observations in a personal log over several additional days to establish a verifiable pattern, then present a written hazard notification to the supervisor with supporting evidence before raising the issue formally, treating evidentiary preparation as a prerequisite to a credible and actionable safety report
Argument structure:
Warrants

The Public Welfare Paramount principle (NSPE Code Section II.1) imposes a duty to hold public safety paramount without qualification as to how the engineer acquired the relevant knowledge, a licensed engineer's obligations are continuous and not suspended outside formal work contexts. The Proactive Risk Disclosure principle demands timely action once a reasonable basis for concern exists. The Incidental Observation Disclosure Obligation establishes that the personal source of the observation does not diminish the professional duty to act. The Design Conformity Obligation (Code Section III.2.b) prohibits Engineer A from completing, signing, or sealing plans that do not conform to applicable engineering and safety standards, including OSHA scaffolding requirements and FHWA work zone safety guidance. The Faithful Agent Obligation to OPQ Construction is a competing but subordinate warrant, requiring Engineer A to follow supervisor direction, but only insofar as doing so does not require acting unethically or endangering public safety.

Rebuttals

Uncertainty arises because the hazard originates from third-party illegal conduct rather than a design defect, and it is arguable that a scaffolding design can be engineered to safely accommodate foreseeable illegal traffic without requiring prior enforcement action, which would dissolve the tension between design completion and hazard resolution. Additionally, the absence of a clear NSPE or BER rule specifying when off-duty observations become on-duty obligations creates ambiguity about the timing and strength of the duty. The Faithful Agent Obligation retains some force as long as the supervisor has not yet been given the opportunity to respond.

Grounds

Engineer A has accepted a scaffolding design assignment for inspection and repair work on a parkway ramp. During his personal commute, he has repeatedly observed commercial vehicles illegally using the parkway in violation of its restricted-use designation. The scaffolding will be erected in proximity to the travel lanes where these vehicles operate. A safety hazard condition exists. The supervisor has directed Engineer A to proceed with the scaffolding design.

Engineer A Public Welfare Paramount Scaffolding Design Obligation Engineer A Scaffolding Design Commercial Vehicle Clearance Safety Obligation

If Engineer A's supervisor dismisses or fails to act on the commercial vehicle hazard notification, should Engineer A escalate through OPQ Construction's internal chain of command before going to the state DOT, or should he treat the supervisor's inaction as sufficient grounds to notify the DOT directly, or stop at documenting his original notification?

Options considered:
O1 Bring the unresolved hazard to higher authority within OPQ Construction first; if internal channels also fail to produce corrective action, notify the state DOT directly in writing as the ultimate contracting authority, without waiting for employer approval to do so. Board's choice
O2 Treat the supervisor's non-response as OPQ Construction management's determination that the hazard does not warrant project modification, and document Engineer A's original notification in writing as a complete discharge of his professional obligation, taking no further escalation steps.
O3 Treat the supervisor's dismissal as evidence that internal channels are ineffective for a public-safety hazard of this magnitude, and notify the state DOT directly without further internal escalation, on the grounds that the systemic nature of the commercial vehicle violation makes employer mediation inappropriate.
Argument structure:
Warrants

The Graduated Escalation Framework established across BER 00-5 and BER 07-10 treats supervisor notification as the first step in a sequenced escalation chain, not the final obligation: if the supervisor fails to act, Engineer A's obligations do not terminate. The Persistent Escalation Obligation When Initial Safety Report Is Unacknowledged requires Engineer A to escalate through internal OPQ Construction channels and, if those fail, to notify the state DOT directly. The Proportional Escalation Obligation calibrates the form and urgency of escalation to the severity and imminence of the hazard relative to BER 00-5, the parkway hazard is real but less certain and less imminent than structural bridge collapse, justifying a measured but still serious multi-step response. The Public Welfare Paramount principle establishes that the obligation to protect public safety does not terminate upon supervisor inaction. The Faithful Agent Obligation to OPQ Construction yields entirely once the supervisor has refused to act on a legitimate safety concern.

Rebuttals

Uncertainty is created by the distinction between a project-specific hazard (where employer mediation is appropriate) and a systemic public-safety condition (where the engineer's obligation to the public may require bypassing the employer). The Proportional Escalation Obligation introduces genuine ambiguity about whether the parkway hazard, involving uncertain probability of collision during a finite inspection window, is sufficiently severe to require external escalation to DOT or law enforcement, or whether internal OPQ Construction channels are sufficient. The Supervisor-Mediated DOT and Law Enforcement Notification Constraint suggests that routing the concern through OPQ Construction (which is the DOT's contractor) may be the appropriate channel even if the supervisor is initially non-responsive.

Grounds

Engineer A has notified his supervisor at OPQ Construction of the commercial vehicle hazard. The supervisor has either dismissed the concern or failed to respond with corrective action. The scaffolding design work is ongoing. The state DOT is the ultimate contracting authority for the project and has both regulatory interest and enforcement capacity over the parkway. The illegal commercial vehicle use is a systemic enforcement gap that predates and extends beyond the specific scaffolding project. In BER 00-5, a non-engineer public works director actively overrode a formal safety closure decision on a condemned bridge, triggering a full multi-authority escalation campaign.

Graduated Escalation Calibrated to Risk Imminence and Employment Context Obligation DOT and Law Enforcement Notification Through Appropriate Responsible Party Obligation

Should Engineer A arrive at the supervisor notification with preliminary design alternatives already prepared and written documentation in hand, notify verbally with contemporaneous documentation but defer alternatives, or notify verbally first and treat both documentation and alternatives as contingent follow-up steps?

Options considered:
O1 Notify the supervisor verbally and simultaneously provide written documentation of the hazard, arriving at the notification conversation with at least a preliminary set of design alternatives, such as clearance modifications or access restrictions, so that the discussion can move immediately to corrective action. Board's choice
O2 Notify the supervisor verbally of the hazard immediately and provide written documentation contemporaneously, but defer development and presentation of design alternatives until after the supervisor has responded, treating hazard identification and solution-generation as sequential rather than simultaneous obligations.
O3 Notify the supervisor verbally of the hazard without waiting to develop design alternatives or prepare written documentation, and provide written follow-up only if the supervisor's verbal response is inadequate or dismissive, treating documentation and alternatives as contingent rather than immediate duties.
Argument structure:
Warrants

The Proactive Design Alternatives Presentation principle, supported by the constructability review standard and OSHA scaffolding requirements, holds that a competent engineer does not merely flag a hazard and await direction, but arrives at the supervisor conversation with a preliminary assessment of mitigation options (increased clearance buffers, physical barriers, phased work scheduling, temporary enforcement requests). This serves two ethical functions: it demonstrates professional judgment rather than upward problem transfer, and it reduces the likelihood that the supervisor will dismiss the concern as impractical. The Written Documentation Requirement, as applied across BER 00-5 and BER 07-10, treats written notification as a core component of the escalation obligation, not an optional supplement, because it creates a contemporaneous record of fulfilled duty, protects Engineer A from subsequent disputes, and creates an institutional record that may prompt action even if the immediate supervisor does not. The Contextual Calibration of Public Safety Reporting principle is a competing warrant suggesting that verbal notification may be sufficient given the relatively lower severity of the present case compared to BER 00-5.

Rebuttals

Uncertainty is created by ambiguity in NSPE Code provisions about whether proactive risk disclosure includes solution-generation or only hazard identification, and by the practical question of whether requiring preliminary design alternatives before notification imposes an unreasonable burden that could itself delay the timely hazard report. The Contextual Calibration principle introduces genuine doubt about whether written documentation is categorically required or whether the board's 'if necessary' qualifier reflects a legitimate contextual judgment that verbal notification is sufficient when the supervisor is immediately accessible and the hazard is not yet imminent. The Engineer A Fact Command Pre-Reporting Readiness Constraint, the expectation that an engineer be able to command the facts before reporting, may support a brief delay for alternative development without constituting a breach of proactive disclosure.

Grounds

Engineer A has accepted the scaffolding design assignment and recognized the commercial vehicle hazard from his commute observations. He is preparing to notify his supervisor. The board's primary conclusion specifies verbal notification 'and in writing if necessary.' The design work is already underway. OSHA scaffolding requirements and FHWA work zone safety guidance require hazard identification and mitigation as part of the design process. BER 00-5 and BER 07-10 both treated written notification as a core component of the escalation obligation.

Pre-Construction Scaffolding Design Safety Hazard Resolution Obligation Engineer A Scaffolding Design Commercial Vehicle Clearance Safety Obligation

Should Engineer A notify his supervisor of the commercial vehicle hazard immediately upon recognizing its relevance to the scaffolding assignment, or should he first spend time compiling a formal evidentiary record from his commute observations before raising the concern?

Options considered:
O1 Immediately notify the supervisor verbally of the commercial vehicle hazard and follow up with written notification contemporaneously or within the same business day, treating the commute observations, however informally acquired, as sufficient evidentiary basis to trigger the duty to act. Board's choice
O2 Spend one to two weeks documenting dates, times, and vehicle types during commutes to compile a formal evidentiary record before raising the concern with the supervisor, so that the notification is grounded in documented evidence rather than informal personal observation.
O3 Raise no formal concern until a site visit or field inspection can confirm that commercial vehicles actually pose a proximate hazard to the scaffolding location, treating commute observations alone as insufficient to trigger a professional duty to notify.
Argument structure:
Warrants

The Public Welfare Paramount principle (NSPE Code Section II.1) imposes a duty to hold public safety paramount without qualification as to how the engineer acquired the relevant knowledge, triggering an obligation to act the moment the commute observations became materially relevant to the active design assignment. The Proactive Risk Disclosure principle demands timely action on credible observations without awaiting formal verification. The Good Faith Safety Concern Threshold requires only a reasonable, non-speculative basis, which repeated firsthand observation of a pattern of illegal vehicle use on the specific affected roadway satisfies. The Incidental Observation Disclosure Obligation confirms that the off-duty source of the observation does not diminish the professional duty. The Written Documentation Requirement establishes that notification should be memorialized in writing as a near-categorical obligation, not merely a contingency. Competing against these is the Faithful Agent Obligation to OPQ Construction, which requires Engineer A to follow supervisor direction and proceed with the assigned design work.

Rebuttals

Uncertainty arises from the absence of a clear NSPE or BER rule specifying when off-duty observations become on-duty obligations. The observation is of third-party illegal conduct rather than a design defect, and the enforcement gap is systemic rather than project-specific. A reasonable engineer might argue that formal verification, documenting dates, times, and vehicle types, is required before raising a concern that could delay a project, and that raising an unverified concern based on commute impressions risks being dismissed as speculative. Additionally, the Good Faith Threshold rebuttal fails only if the observed hazard is sufficiently proximate and credible that any reasonable engineer would act without further verification.

Grounds

Engineer A has accepted a scaffolding design assignment for inspection and repair work on a parkway ramp. During his personal commute, he has repeatedly observed commercial vehicles illegally using the parkway in violation of posted restrictions. The scaffolding will be erected in proximity to the travel lanes where these vehicles operate. The supervisor has directed Engineer A to proceed with the design. No formal site inspection has been conducted to document the illegal vehicle use.

Engineer A Pre-Construction Scaffolding Hazard Resolution Present Case Incidental Observation Disclosure Obligation Invoked By Engineer A Commute Observation

After notifying his supervisor of the commercial vehicle hazard, should Engineer A condition finalization and sealing of the scaffolding design on formal acknowledgment and corrective action by OPQ Construction, or should he proceed with design completion under supervisor direction, potentially incorporating design accommodations for the foreseeable illegal traffic without requiring prior enforcement action?

Options considered:
O1 Condition finalization and sealing of the scaffolding design on the supervisor's formal acknowledgment of the commercial vehicle hazard and adoption of at least one corrective measure, physical design modification, traffic control plan, or DOT coordination, and present preliminary alternative design configurations alongside the hazard notification to facilitate that resolution Board's choice
O2 Proceed with finalizing and sealing the scaffolding design, incorporating conservative clearance buffers and physical protective barriers sufficient to accommodate foreseeable commercial vehicle dimensions, treating the design accommodation itself as the corrective measure without requiring separate supervisor acknowledgment or enforcement action
O3 Proceed with design development but not finalization or sealing, submitting a preliminary design package to the supervisor with a written notation that the plans are not ready for sealing pending resolution of the identified commercial vehicle hazard, thereby maintaining project momentum while formally preserving Engineer A's professional objection in the project record
Argument structure:
Warrants

The Non-Acquiescence to Unsafe Client Directives principle requires Engineer A to resist supervisor pressure to finalize a design that does not account for a foreseeable safety hazard. The Design Conformity Obligation under Code Section III.2.b independently prohibits sealing plans that fail to conform to applicable engineering and safety standards, including OSHA and FHWA requirements that treat hazard identification and mitigation as integral to the design process. The Proactive Design Alternatives Presentation principle supports Engineer A arriving at the supervisor conversation with preliminary mitigation options: increased clearance buffers, physical barriers, phased scheduling, or DOT traffic control requests, rather than simply flagging the hazard and awaiting direction. Competing against these is the Faithful Agent Obligation, which requires Engineer A to follow supervisor direction and serve OPQ Construction's project timeline, and the possibility that the scaffolding design can be engineered to safely accommodate foreseeable illegal traffic without requiring prior enforcement action, which would dissolve the conflict between design completion and hazard resolution.

Rebuttals

Uncertainty is created by the possibility that a competent scaffolding design incorporating adequate clearance buffers and physical protective measures could fully neutralize the foreseeable risk from illegal commercial vehicles, such that sealing the design would not constitute a conformity violation. If the design itself can absorb the hazard through engineering controls, the argument for conditioning finalization on supervisor acknowledgment or enforcement action weakens substantially. Additionally, the Faithful Agent Obligation retains some force where the supervisor's direction to proceed is not itself an instruction to produce an unsafe design but rather a direction to apply engineering judgment to accommodate foreseeable conditions, a standard professional task.

Grounds

Engineer A has notified his supervisor of the commercial vehicle hazard. The supervisor has directed Engineer A to proceed with the scaffolding design as assigned. The hazard has not been formally acknowledged, and no corrective measures, physical design modifications, traffic control, or DOT coordination, have been adopted. NSPE Code Section III.2.b prohibits Engineer A from completing, signing, or sealing plans not in conformity with applicable engineering standards. OSHA scaffolding requirements and FHWA work zone safety guidance require foreseeable hazard identification and mitigation as part of the design process.

Engineer A Pre-Construction Scaffolding Hazard Resolution Present Case Engineer A Supervisor Non-Response Scaffolding Design Finalization Prohibition

When Engineer A receives the scaffolding design assignment and recognizes that his repeated personal commute observations of illegal commercial vehicle use on the parkway are materially relevant to that assignment, what action must he take, and does the informal, off-duty source of those observations affect the strength or timing of that obligation?

Options considered:
O1 Immediately notify the supervisor verbally and in writing of the commercial vehicle hazard upon recognizing its relevance to the scaffolding assignment, treating repeated personal commute observations as sufficient evidentiary basis without awaiting formal verification Board's choice
O2 Conduct a structured personal documentation effort over several additional commutes, logging dates, times, vehicle types, and estimated clearances, before raising the concern with the supervisor, in order to present a credible and defensible evidentiary record rather than an anecdotal report
O3 Raise the commercial vehicle observation informally with the supervisor as a preliminary design consideration, framing it as a factor to investigate during the formal site inspection phase rather than as an immediate safety notification, while proceeding with initial design scoping
Argument structure:
Warrants

The Incidental Observation Disclosure Obligation and Proactive Risk Disclosure principle hold that a licensed engineer carries professional responsibilities continuously, knowledge acquired off-duty that is materially relevant to an active design assignment creates an immediate duty to act, regardless of how it was acquired. The Good Faith Safety Concern Threshold principle holds that repeated firsthand observation of a pattern of illegal vehicle use on the specific affected roadway satisfies the evidentiary minimum without requiring formal verification, vehicle counts, or instrumented measurement. The Contextual Calibration of Public Safety Reporting principle and the Faithful Agent Obligation to OPQ Construction both suggest that the supervisor is the appropriate first point of contact, and that routing the concern through the employer is the proper initial channel before any external escalation.

Rebuttals

Uncertainty arises because no NSPE rule explicitly specifies when off-duty observations become on-duty obligations, and because the hazard originates from third-party illegal conduct rather than a design defect within Engineer A's control. A reasonable engineer might conclude that informal, unverified personal observations do not yet meet the evidentiary standard for a formal professional notification, particularly where the frequency, vehicle dimensions, and proximity to the proposed scaffolding footprint have not been formally assessed. Additionally, the Faithful Agent Obligation might be read to counsel waiting until the design assignment is further developed before raising concerns that could disrupt the project timeline.

Grounds

Engineer A has accepted a scaffolding design assignment for bridge inspection work on a state parkway. During his personal daily commute on that same parkway, he has repeatedly observed commercial vehicles using the roadway in violation of its restricted-use designation. A safety hazard condition exists because those vehicles would pass in close proximity to workers on the scaffolding during the inspection period. Engineer A has not conducted a formal site inspection; his observations are incidental and off-duty.

Engineer A Incidental Commute Observation Safety Reporting Present Case Engineer A Good Faith Safety Concern External Reporting Threshold Assessment
16 sequenced 9 actions 7 events
Case timeline
In BER Case 07-10, a structural modification is made to a barn after it has been built and sold, creating a safety hazard that the original engineer later discovers. This event initiates a timeline spanning at least four years before the engineer provides belated safety notification.
In BER Case 00-5, a bridge is found to be in a deteriorating structural condition, triggering a series of escalating safety responses by the local government engineer. This discovery initiates the graduated ethical response timeline used as precedent.
In BER Case 00-5, upon receiving the bridge inspector's call identifying critically rotten pilings, Engineer A immediately directed the erection of barricades and closed bridge signs within the hour on a Friday afternoon, preventing public access to the dangerous structure.
Fulfills (3)
  • NSPE Code obligation to hold paramount the safety, health, and welfare of the public
  • Obligation as public employee to take immediate protective action for imminent structural danger
  • Duty to act decisively when life safety is at immediate risk
In BER Case 00-5, bridge closure barricades erected by the engineer are removed by an unknown party, reinstating public access to the unsafe bridge and requiring the engineer to reinstall them. This event demonstrates that safety measures can be actively undermined, escalating the engineer's duty.
In BER Case 00-5, after discovering on the following Monday that barricades had been dumped in the river and the closed sign removed, Engineer A directed the installation of more permanent barricades and signs to restore the bridge closure.
Fulfills (3)
  • NSPE Code obligation to hold paramount the safety, health, and welfare of the public
  • Obligation not to bow to public pressure when fundamental safety is at stake
  • Persistent duty to maintain protective measures against known hazard
In BER Case 00-5, within three weeks of the initial closure, Engineer A successfully obtained authorization for the bridge to be replaced, initiating the formal process for a permanent structural solution to the safety hazard.
Fulfills (3)
  • Obligation to pursue permanent corrective action, not merely temporary mitigation
  • NSPE Code obligation to hold paramount the safety, health, and welfare of the public
  • Duty as public employee to advocate for adequate resources to address known structural deficiencies
In BER Case 00-5, a non-engineer public works director decided to have a retired bridge inspector (also not an engineer) examine the bridge and then ordered the installation of two crutch piles and reopened the bridge with a five-ton limit, without follow-up inspection. This is a volitional professional decision with significant ethical implications.
Fulfills (1)
  • Responding to community access needs and political pressure
Violates (4)
  • Obligation to use licensed engineers for structural safety determinations affecting public safety
  • Obligation not to reopen public infrastructure without adequate engineering verification
  • Prohibition on unlicensed practice of engineering (by relying on non-engineer inspector for structural determination)
  • Obligation to implement follow-up inspection after structural modification
In BER Case 00-5, a non-engineer Public Works Director orders the installation of crutch piles as a temporary remediation measure for the deteriorating bridge, overriding or supplementing the engineer's professional judgment. This represents an institutional response that may be insufficient or inappropriate.
Engineer A personally observes commercial vehicles illegally using the parkway during his daily commute, both prior to and during his scaffolding assignment. This repeated observation creates direct personal knowledge of an ongoing safety hazard.
Engineer A is assigned by OPQ Construction to design inspection and construction scaffolding for a parkway cloverleaf ramp, placing him in direct professional proximity to the hazard he has already observed. This assignment fuses his personal knowledge with formal professional responsibility.
The combination of commercial vehicles illegally using the parkway and the planned scaffolding installation creates an objectively dangerous condition: overweight or oversized vehicles passing through or near active construction scaffolding not designed for such loads or clearances. This is the core hazardous state that drives the ethical dilemma.
Engineer A's supervisor at OPQ Construction directs Engineer A to design inspection and construction scaffolding for the parkway cloverleaf ramp without apparent consideration of the commercial vehicle hazard. This constitutes a volitional professional decision to assign the design task and implicitly set its scope.
At stake (3)
  • Obligation to ensure worker safety before assigning design tasks in potentially hazardous conditions
  • Obligation to assess site-specific risks prior to directing engineering work
  • NSPE Code obligation to hold paramount the safety, health, and welfare of the public
Fulfills (2)
  • Contractual obligation to state DOT to initiate assigned work
  • Organizational duty to direct subordinate engineers on project tasks
Engineer A accepts the supervisor's directive to design the inspection and construction scaffolding despite having personal knowledge of the commercial vehicle hazard on the parkway. This decision to proceed, even tentatively, without immediately raising concerns constitutes a volitional professional act.
At stake (3)
  • NSPE Code obligation to hold paramount the safety, health, and welfare of the public
  • Obligation to immediately notify supervisor of known safety hazards before proceeding with design
  • Obligation not to undertake engineering work under conditions known to be unsafe without first seeking corrective action
Fulfills (2)
  • Preliminary compliance with employer directive
  • Internal recognition of safety hazard consistent with professional awareness obligation
Engineer A should verbally (and in writing if necessary) notify his immediate supervisor at OPQ Construction of the safety hazard posed by illegal commercial vehicles passing the proposed scaffolding site before design and assembly proceeds. This is the primary recommended action identified in the discussion.
Fulfills (4)
  • NSPE Code obligation to hold paramount the safety, health, and welfare of the public
  • Obligation to notify employer of safety hazards known to the engineer
  • Obligation to act before unsafe conditions are embedded in the design
  • Duty of candor and professional honesty with employer
If internal notification to the supervisor is insufficient or unacted upon, Engineer A or an appropriate responsible party within OPQ Construction should notify state department of transportation officials and law enforcement so that corrective measures, such as heightened enforcement, traffic closure, or design accommodation, can be implemented before scaffolding assembly begins.
Fulfills (4)
  • NSPE Code obligation to hold paramount the safety, health, and welfare of the public
  • Obligation to escalate safety concerns to authorities with power to act when internal channels are insufficient
  • Obligation to protect construction workers as well as the general public
  • Professional duty not to proceed with design under known unsafe conditions without seeking corrective action
As one potential corrective measure, Engineer A could design the scaffolding to accommodate the possibility of commercial vehicles passing by, rather than relying solely on external enforcement to eliminate the hazard. This is identified in the discussion as one option among several for protecting workers.
At stake (1)
  • Potential concern that designing for illegal use without simultaneously advocating for enforcement could be seen as accepting an unsafe status quo
Fulfills (3)
  • Obligation to protect the safety of construction workers through engineering design
  • NSPE Code obligation to hold paramount the safety, health, and welfare of the public
  • Obligation to apply engineering competence to mitigate foreseeable hazards
Narrative (2 main characters)
View Extraction
Opening Context

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

You are Engineer A, a licensed professional engineer employed by OPQ Construction, a contractor hired by the state department of transportation to inspect and repair highway and parkway on and off ramps. Your supervisor has directed you to design inspection and construction scaffolding for a noncommercial parkway cloverleaf ramp that has limited height and width clearance. During your regular commute on this parkway, you have repeatedly observed commercial vehicles illegally operating on it, despite the prohibition on such vehicles. You are concerned that if a commercial vehicle passes the scaffolding during inspection or construction work, it could endanger employees on the scaffolding as well as others nearby. The decisions you face involve how to handle this observed hazard in relation to your design responsibilities and your obligations to your employer and the public.

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.

OPQ Construction Roles in this case: DOT Inspection Repair EmployerSupervisor Employer RelationshipSupervisor Present Case

The constraint holds that because commercial vehicles are legally prohibited from the parkway, Engineer A is not required to design scaffolding clearances that accommodate them — the illegal use is a third-party violation outside the design envelope. Yet the obligation to ensure commercial vehicle clearance safety in the scaffolding design is grounded in the observed empirical reality that commercial vehicles do in fact use the parkway, as Engineer A witnessed during the commute. Designing only to the legal use case while knowing that illegal use is occurring foreseeably exposes the public to serious harm. Fulfilling the design obligation requires treating observed reality as the operative safety parameter, directly contradicting the constraint that limits design scope to lawful traffic. This is a core dilemma between legal compliance as a design boundary and foreseeable harm prevention as an engineering duty.

Attaches to role: DOT Inspection Repair Employer

Engineer A has a positive duty not to acquiesce when the supervisor refuses to act on the commercial vehicle clearance hazard, requiring escalation beyond the employment chain. However, the constraint governing external escalation in the present case conditions that escalation on supervisor non-response rather than supervisor refusal, creating ambiguity about whether active refusal triggers the same pathway as silence. Fulfilling the non-acquiescence obligation may require Engineer A to bypass the supervisor entirely and contact DOT or law enforcement directly, while the constraint implies a structured, supervisor-mediated or sequenced escalation process that has not yet been exhausted. The tension is genuine because acting too early risks violating the graduated escalation norm, while waiting risks allowing a dangerous scaffolding design to be finalized.

Attaches to role: Supervisor Employer Relationship

The graduated escalation obligation requires Engineer A to proceed through internal channels — notifying the supervisor in writing, presenting alternative designs, and allowing the employer an opportunity to respond — before escalating externally, in recognition of the employment relationship and proportionality norms. The public welfare paramount obligation, however, places the safety of the passing public and construction workers above all other considerations, including employment hierarchy and procedural sequencing. When the risk is sufficiently imminent and severe, the public welfare obligation may demand immediate external reporting to DOT or law enforcement, collapsing the graduated sequence. These two obligations are in genuine tension because the speed and directness required by public welfare primacy conflicts with the deliberate, stepwise patience required by graduated escalation, and Engineer A cannot fully satisfy both simultaneously when the hazard is active and the supervisor is unresponsive.

Attaches to role: DOT Inspection Repair Employer
Engineer A Roles in this case: Construction Scaffolding Design EngineerBER 00-5 Local Government Bridge EngineerBER 07-10 Prior Design Engineer BarnPresent Case OPQ Construction Scaffolding Designer

Engineer A has a positive duty not to acquiesce when the supervisor refuses to act on the commercial vehicle clearance hazard, requiring escalation beyond the employment chain. However, the constraint governing external escalation in the present case conditions that escalation on supervisor non-response rather than supervisor refusal, creating ambiguity about whether active refusal triggers the same pathway as silence. Fulfilling the non-acquiescence obligation may require Engineer A to bypass the supervisor entirely and contact DOT or law enforcement directly, while the constraint implies a structured, supervisor-mediated or sequenced escalation process that has not yet been exhausted. The tension is genuine because acting too early risks violating the graduated escalation norm, while waiting risks allowing a dangerous scaffolding design to be finalized.

Attaches to role: Construction Scaffolding Design Engineer

The constraint holds that because commercial vehicles are legally prohibited from the parkway, Engineer A is not required to design scaffolding clearances that accommodate them — the illegal use is a third-party violation outside the design envelope. Yet the obligation to ensure commercial vehicle clearance safety in the scaffolding design is grounded in the observed empirical reality that commercial vehicles do in fact use the parkway, as Engineer A witnessed during the commute. Designing only to the legal use case while knowing that illegal use is occurring foreseeably exposes the public to serious harm. Fulfilling the design obligation requires treating observed reality as the operative safety parameter, directly contradicting the constraint that limits design scope to lawful traffic. This is a core dilemma between legal compliance as a design boundary and foreseeable harm prevention as an engineering duty.

Attaches to role: Construction Scaffolding Design Engineer

Tension between Engineer A Public Welfare Paramount Scaffolding Design Obligation and Engineer A Scaffolding Design Commercial Vehicle Clearance Safety Obligation

Attaches to role: Construction Scaffolding Design Engineer

Tension between Pre-Construction Scaffolding Design Safety Hazard Resolution Obligation and Engineer A Scaffolding Design Commercial Vehicle Clearance Safety Obligation

Attaches to role: Construction Scaffolding Design Engineer

Tension between Engineer A Pre-Construction Scaffolding Hazard Resolution Present Case and Engineer A Supervisor Non-Response Scaffolding Design Finalization Prohibition

Attaches to role: Construction Scaffolding Design Engineer

Tension between Engineer A Scaffolding Design Commercial Vehicle Clearance Safety Present Case and Engineer A Supervisor Non-Response Scaffolding Design Finalization Prohibition

Attaches to role: Construction Scaffolding Design Engineer

The graduated escalation obligation requires Engineer A to proceed through internal channels — notifying the supervisor in writing, presenting alternative designs, and allowing the employer an opportunity to respond — before escalating externally, in recognition of the employment relationship and proportionality norms. The public welfare paramount obligation, however, places the safety of the passing public and construction workers above all other considerations, including employment hierarchy and procedural sequencing. When the risk is sufficiently imminent and severe, the public welfare obligation may demand immediate external reporting to DOT or law enforcement, collapsing the graduated sequence. These two obligations are in genuine tension because the speed and directness required by public welfare primacy conflicts with the deliberate, stepwise patience required by graduated escalation, and Engineer A cannot fully satisfy both simultaneously when the hazard is active and the supervisor is unresponsive.

Attaches to role: Construction Scaffolding Design Engineer

Tension between Engineer A Supervisor Non-Response Scaffolding Safety External Escalation Present Case and Proportional Escalation Obligation Present Case vs BER 00-5

Attaches to role: Construction Scaffolding Design Engineer

Tension between Engineer A BER 00-5 Full-Bore Multi-Authority Campaign Bridge Collapse and Engineer A BER 07-10 Deadline-Conditioned Escalation County State Building Officials

Attaches to role: Construction Scaffolding Design Engineer

Tension between Engineer A Pre-Construction Scaffolding Hazard Resolution Present Case and Incidental Observation Disclosure Obligation Invoked By Engineer A Commute Observation

Attaches to role: Construction Scaffolding Design Engineer

Tension between Engineer A Incidental Commute Observation Safety Reporting Present Case and Engineer A Good Faith Safety Concern External Reporting Threshold Assessment

Attaches to role: Construction Scaffolding Design Engineer

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

Guided by: Public Welfare Paramount, Construction Safety Awareness in Structural Design, Proactive Risk Disclosure

Engineer A has a positive duty not to acquiesce when the supervisor refuses to act on the commercial vehicle clearance hazard, requiring escalation beyond the employment chain. However, the constraint governing external escalation in the present case conditions that escalation on supervisor non-response rather than supervisor refusal, creating ambiguity about whether active refusal triggers the same pathway as silence. Fulfilling the non-acquiescence obligation may require Engineer A to bypass the supervisor entirely and contact DOT or law enforcement directly, while the constraint implies a structured, supervisor-mediated or sequenced escalation process that has not yet been exhausted. The tension is genuine because acting too early risks violating the graduated escalation norm, while waiting risks allowing a dangerous scaffolding design to be finalized.

The constraint holds that because commercial vehicles are legally prohibited from the parkway, Engineer A is not required to design scaffolding clearances that accommodate them — the illegal use is a third-party violation outside the design envelope. Yet the obligation to ensure commercial vehicle clearance safety in the scaffolding design is grounded in the observed empirical reality that commercial vehicles do in fact use the parkway, as Engineer A witnessed during the commute. Designing only to the legal use case while knowing that illegal use is occurring foreseeably exposes the public to serious harm. Fulfilling the design obligation requires treating observed reality as the operative safety parameter, directly contradicting the constraint that limits design scope to lawful traffic. This is a core dilemma between legal compliance as a design boundary and foreseeable harm prevention as an engineering duty.

The graduated escalation obligation requires Engineer A to proceed through internal channels — notifying the supervisor in writing, presenting alternative designs, and allowing the employer an opportunity to respond — before escalating externally, in recognition of the employment relationship and proportionality norms. The public welfare paramount obligation, however, places the safety of the passing public and construction workers above all other considerations, including employment hierarchy and procedural sequencing. When the risk is sufficiently imminent and severe, the public welfare obligation may demand immediate external reporting to DOT or law enforcement, collapsing the graduated sequence. These two obligations are in genuine tension because the speed and directness required by public welfare primacy conflicts with the deliberate, stepwise patience required by graduated escalation, and Engineer A cannot fully satisfy both simultaneously when the hazard is active and the supervisor is unresponsive.

Engineer A has a positive duty not to acquiesce when the supervisor refuses to act on the commercial vehicle clearance hazard, requiring escalation beyond the employment chain. However, the constraint governing external escalation in the present case conditions that escalation on supervisor non-response rather than supervisor refusal, creating ambiguity about whether active refusal triggers the same pathway as silence. Fulfilling the non-acquiescence obligation may require Engineer A to bypass the supervisor entirely and contact DOT or law enforcement directly, while the constraint implies a structured, supervisor-mediated or sequenced escalation process that has not yet been exhausted. The tension is genuine because acting too early risks violating the graduated escalation norm, while waiting risks allowing a dangerous scaffolding design to be finalized.

The constraint holds that because commercial vehicles are legally prohibited from the parkway, Engineer A is not required to design scaffolding clearances that accommodate them — the illegal use is a third-party violation outside the design envelope. Yet the obligation to ensure commercial vehicle clearance safety in the scaffolding design is grounded in the observed empirical reality that commercial vehicles do in fact use the parkway, as Engineer A witnessed during the commute. Designing only to the legal use case while knowing that illegal use is occurring foreseeably exposes the public to serious harm. Fulfilling the design obligation requires treating observed reality as the operative safety parameter, directly contradicting the constraint that limits design scope to lawful traffic. This is a core dilemma between legal compliance as a design boundary and foreseeable harm prevention as an engineering duty.

The graduated escalation obligation requires Engineer A to proceed through internal channels — notifying the supervisor in writing, presenting alternative designs, and allowing the employer an opportunity to respond — before escalating externally, in recognition of the employment relationship and proportionality norms. The public welfare paramount obligation, however, places the safety of the passing public and construction workers above all other considerations, including employment hierarchy and procedural sequencing. When the risk is sufficiently imminent and severe, the public welfare obligation may demand immediate external reporting to DOT or law enforcement, collapsing the graduated sequence. These two obligations are in genuine tension because the speed and directness required by public welfare primacy conflicts with the deliberate, stepwise patience required by graduated escalation, and Engineer A cannot fully satisfy both simultaneously when the hazard is active and the supervisor is unresponsive.


These tensions did not map cleanly to a single character.

Tension between Supervisor Non-Response Scaffolding Safety External Escalation Obligation and Supervisor-Mediated DOT and Law Enforcement Notification Constraint

Tension between Graduated Escalation Calibrated to Risk Imminence and Employment Context Obligation and DOT and Law Enforcement Notification Through Appropriate Responsible Party Obligation

Opening States (10)
Restricted-Use Infrastructure Enforcement Gap State Engineer A Observed Illegal Commercial Vehicle Use Creating Scaffolding Hazard Observed Illegal Third-Party Conduct Creating Worksite Hazard State Parkway Restricted-Use Enforcement Gap Engineer A Public Safety at Risk - Worker and Public Endangerment from Scaffolding Proximity to Illegal Traffic Engineer A Unverified Concern - Scaffolding Hazard Not Yet Formally Reported Engineer A Client Relationship with OPQ Construction and State DOT Graduated Danger Severity Calibration State Worksite Hazard Requiring Pre-Design Corrective Action State Bridge Closure Public Pressure Override - BER 00-5
Summary
  • Engineers facing unresponsive supervisors on safety-critical issues must escalate through organizational channels before bypassing the chain of command, but the threshold for direct external notification compresses dramatically as risk imminence increases.
  • The oscillation transformation reveals that public welfare obligations and commercial constraints are not simply hierarchical but dynamically interact, requiring engineers to continuously recalibrate their response as situational facts evolve.
  • Written documentation of verbal safety notifications is not merely procedural formality but serves as both an ethical safeguard and a legal protection that preserves the engineer's ability to demonstrate good-faith escalation.