Step 4: Full View

The 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.

In 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.

Beyond 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.

In 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.

The 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.

The 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.

In 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.

The 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.

In 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.

In 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.

The 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.

In 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.

The 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.

In 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.

The 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.

The 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.

In 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.

The 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.

In 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.

In 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.

In 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.

The 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.

In 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.

In 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.

In 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.

In 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.

In 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.