Step 4: Review

Hold paramount the safety, health, and welfare of the public.

Issue public statements only in an objective and truthful manner.

Avoid deceptive acts.

Engineers shall not permit the use of their name or associate in business ventures with any person or firm that they believe is engaged in fraudulent or dishonest enterprise.

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.

Engineers shall be objective and truthful in professional reports, statements, or testimony. They shall include all relevant and pertinent information in such reports, statements, or testimony, which should bear the date indicating when it was current.

Engineers shall advise their clients or employers when they believe a project will not be successful.

Engineers shall avoid the use of statements containing a material misrepresentation of fact or omitting a material fact.

Engineers shall not attempt to injure, maliciously or falsely, directly or indirectly, the professional reputation, prospects, practice, or employment of other engineers. Engineers who believe others are guilty of unethical or illegal practice shall present such information to the proper authority for action.

Cited to explore whether the Code applies to firms providing sub-professional (non-engineering) services, as was the case with Firm DBA's public relations work.

Cited to support the conclusion that the Code applies universally to all NSPE members regardless of differing circumstances, supporting the finding that Firm DBA (with PE ownership/supervision) must abide by the Code despite providing non-engineering services.

Cited by analogy to establish that Engineer M, like the engineer in that case, has an ongoing duty to hold paramount the safety, health, and welfare of the public even when removed from direct responsibility or facing resistance.

Cited by analogy to support the recommended course of action for Engineer M, showing that an engineer should first seek clarification from the party in question and, if unsatisfied, report the matter to the state licensure board.

Cited to support the principle that a registered professional's report must include relevant and pertinent information to protect public safety, health, and welfare, directly applicable to the omissions in Firm DBA's report.

Engineer M should challenge the validity of Firm DBA’s report as Firm DBA did not abide by the Code in a number of instances.

Engineer M should first confer with Firm DBA to correct all discrepancies in the report. If no agreement can be made going forward, Engineer M should confer with the City to outline the ethical obligations. Engineer M should also consider any obligations they may have to report to the state licensure board.

The actions of Firm DBA are not ethical under the Code as the services provided were under the supervision and ownership of licensed professional engineers.

The Board's recommendation that Engineer M confer with the City about ethical obligations should be extended to recognize that the City itself may bear independent ethical responsibility. The City's explicit directive to conduct outreach sessions in a manner that disadvantaged Community P was not merely a business preference but effectively directed a violation of public welfare and objectivity principles. Engineer M's duty to escalate to the City therefore should not be framed only as informing a client of a consultant's Code violations, but as confronting the client's own role in causing those violations, which may require Engineer M to document the City's directive separately from Firm DBA's report failures.

The Board's conclusion that Firm DBA's actions are unethical because the firm is owned and supervised by licensed engineers should be extended to address the structural mechanism of evasion at issue: organizing outreach functions under a nominally non-engineering 'communications and public relations' department does not exempt those activities from Code scrutiny. Because licensed engineers retain supervisory and ownership control over that department, the Code's public welfare and objectivity obligations attach to the department's outputs as professional services performed under the firm's engineering practice, regardless of internal labeling. Permitting such organizational separations to shield outreach or communications work from ethical accountability would create an loophole undermining the Code's intent wherever firms diversify into adjacent service lines.

The Board's recommendation that Engineer M first attempt correction with Firm DBA and only later consider licensure board reporting understates the significance of the sequence of events already completed: Engineer M raised concerns, Firm DBA dismissed them, and a misleading report was submitted despite that dismissal. This sequence arguably already satisfies the threshold for a mandatory reporting obligation under II.1.f, since Engineer M has actual knowledge of a Code violation that was not remedied through informal means before submission. The Board's phased approach may therefore understate the urgency of Engineer M's reporting duty, particularly given that the report has already been submitted to the City and may be relied upon in decisions affecting Community P's displacement risk.

Regarding Q101: The City's directive to schedule outreach sessions in ways that disadvantage Community P raises a distinct ethical concern from Firm DBA's reporting deficiencies. While Firm DBA bears direct Code responsibility for executing and reporting on the sessions, the City's instruction—motivated by economic, political, and social considerations—suggests the client itself directed an inequitable process. Engineer M's obligation to hold paramount public welfare (I.1) means this should not be treated merely as an internal firm problem; Engineer M has an independent duty to raise this directly with the City as the client, separate from any corrective dialogue with Firm DBA.

Regarding Q103: Firm DBA's structural placement of outreach activities within a nominally non-engineering 'communications and public relations' department does not shield the firm from Code obligations. Because licensed professional engineers supervise and own all departments, including this one, the substance of the activity—informing a professional engineering report used to justify a public infrastructure decision—triggers Code applicability regardless of internal departmental labels. Permitting such organizational separations to evade accountability would create an exploitable loophole undermining the Code's intent to protect public welfare wherever licensed engineers direct or control the underlying work product.

Regarding Q104: Although Community P is not Engineer M's contractual client, Engineer M owes it an obligation grounded in the Code's paramount duty to public welfare (I.1). This obligation is not diminished by the absence of a direct contractual relationship; it requires Engineer M to ensure that decisions materially affecting Community P's displacement and economic disruption are based on an honest and complete factual record, and to escalate concerns when that record is compromised.

Regarding Q201: Firm DBA's deference to the City's political and economic preferences does not excuse the omission of material outreach details from its report. The Code's requirement of honesty in public statements (I.3, II.3.a) is not subordinate to a client's business or political preferences; even where a client directs the format or venue of outreach, the engineer's duty to truthfully report the process and its limitations remains independent and non-negotiable.

Regarding Q203: Firm DBA cannot avoid Code scrutiny by asserting its public relations department was not performing 'engineering services.' Because the department's outreach data directly fed into and shaped an engineering report relied upon for infrastructure decision-making, and because licensed engineers supervised and owned the department, the activity falls within the scope of professional practice governed by the Code. The public welfare obligation in I.1 and objectivity requirement in II.3.a extend to all firm activities that materially inform engineering judgments, irrespective of internal departmental characterization.

Regarding Q301: From a deontological standpoint, Firm DBA violated its duty of complete and truthful reporting under I.3, II.3.a, and III.3.a. These provisions impose a categorical obligation to disclose material facts regardless of consequences; omitting session times, locations, and the absence of a written-comment method constitutes a failure of duty independent of whether the omissions changed the ultimate outcome or were directed by the City.

Regarding Q304: Once informal correction attempts with Firm DBA fail, Engineer M's duty under II.1.f to report known Code violations to appropriate authorities takes precedence over any professional courtesy or business relationship with Firm DBA. The Code does not permit collegial loyalty to override the obligation to protect the integrity of the profession and public welfare when a documented violation persists uncorrected.

Regarding Q401: Even if the City had not specifically directed the manner of outreach, Firm DBA would still bear independent responsibility under the Code for the deficiencies in its public engagement process and report. The Code's objectivity and completeness requirements (I.3, II.3.a, III.3.a) attach to the engineer's own professional judgment and reporting conduct, not merely to client instructions; a client directive does not transfer or dilute the engineer's personal accountability for truthful representation.

Regarding Q403: Even if Firm DBA's notices had included a method for written comment submission, the report's claim of Community P's support would likely still constitute a material misrepresentation under III.3.a, given that the sessions were held at inaccessible times and locations far from Community P, and no virtual option was offered. The core violation lies in the systemic barriers to genuine participation, not solely in the absence of a written-comment channel.

The case demonstrates that client directives, even when framed as legitimate business, economic, or political considerations, cannot subordinate the engineering duties of objectivity and complete reporting. Firm DBA attempted to resolve the tension between satisfying the City's preferences and maintaining honest reporting by omitting material facts rather than either refusing the City's directive or accurately reporting the deficient process. This resolution was improper: the Code does not permit engineers to trade away truthful reporting for client satisfaction, meaning that when such tensions arise, the duty to the public and to honest documentation must prevail over accommodating a client's political or economic preferences.

The tension between Firm DBA's claim that its public relations department was not performing 'engineering services' and the Board's application of the Code to that department is resolved by anchoring accountability in firm structure rather than departmental labeling. Because licensed professional engineers held supervisory and ownership control over all departments, including the communications unit, the Public Welfare principle attaches to the firm's overall conduct rather than being confined to activities formally labeled as engineering. This establishes that organizational subdivision cannot be used to wall off non-technical functions from Code obligations when those functions are ultimately controlled by licensed engineers and materially affect public welfare outcomes like community displacement risk.

Professional Dignity in Community P Outreach and Objectivity in DBA Report were not actually in tension despite surface appearances; rather, honoring Community P's dignity required objective reporting, and it was only Firm DBA's choice to conceal outreach deficiencies that created an apparent conflict. Had Firm DBA disclosed the true scheduling, location, and comment-method limitations, the report would have simultaneously respected Community P's stake in the process and satisfied objectivity requirements. This suggests that in engagement-based engineering work, transparency about process limitations is not merely a reporting formality but a mechanism through which respect for an affected community's dignity and objective professional practice are jointly achieved.

Should Engineer M challenge the validity of Firm DBA’s report?

Should Engineer M raise any concerns with the City, as the client, and, if so, how?

Are Firm DBA’s actions ethical? Even though Firm DBA is not providing engineering services, are they required to abide by NSPE’s Code of Ethics?

Does the City's explicit directive to hold outreach sessions in a way that disadvantages Community P constitute an independent ethical violation by the City that Engineer M must address, separate from Firm DBA's report deficiencies?

Should Engineer M have withdrawn from or refused continued association with Firm DBA once Firm DBA dismissed Engineer M's concerns and proceeded with a misleading report?

Does Firm DBA's use of a nominally non-engineering 'communications and public relations' department to conduct outreach represent a structural attempt to evade engineering ethics obligations, and should such organizational separations be permitted to shield licensed firms from Code accountability?

What direct ethical obligations, if any, does Engineer M owe to Community P as an affected but non-client stakeholder, distinct from Engineer M's contractual obligations to the City?

How should Honesty in Support Claim be balanced against Firm DBA's deference to the City's directive to conduct outreach sessions favoring an alternate route for economic and political reasons?

Does Complete Reporting in Engagement Report conflict with Firm DBA's apparent obligation to satisfy the City's business preferences and prior project practices?

How should Public Welfare Applying Code to DBA be reconciled with Firm DBA's position that its public relations department is not itself performing 'engineering services' and thus arguably outside Code scrutiny?

How should Professional Dignity in Community P Outreach be balanced against Objectivity in DBA Report when accurately reporting the outreach process would itself reveal harm to Community P's dignity and interests?

From a deontological perspective, did Firm DBA fulfill its duty of complete and truthful reporting under Code provisions I.3, II.3.a, and III.3.a when it omitted the times, locations, and lack of a written-comment method from its public engagement report?

From a consequentialist perspective, does the outcome of securing City approval for the highway route through Community P justify Firm DBA's selective omission of scheduling and accessibility details in its report, given the resulting risk of displacement and disruption to an already overburdened community?

Did Engineer M act with professional integrity, in a virtue-ethics sense, by voicing concerns to Firm DBA about the outreach process even though the objection did not prevent the report's submission or change the outcome?

From a deontological standpoint, does Engineer M's duty under II.1.f to report known Code violations to the appropriate authorities take precedence over the professional courtesy owed to Firm DBA as a business partner, once informal correction attempts fail?

If the City had not specifically instructed Firm DBA to conduct the outreach sessions in that manner, would the Board still conclude that Firm DBA's actions were unethical, or would the City's directive have diluted Firm DBA's independent responsibility under the Code?

If Firm DBA's communications and public relations department had not been staffed by licensed professional engineers in supervisory and ownership roles, would the Board still find that Firm DBA was obligated to abide by the NSPE Code of Ethics for these outreach activities?

If Firm DBA's outreach notices had provided a method for written comment submission, would the Board still find the report's claim of Community P's support to be a material misrepresentation under III.3.a?

If the public engagement sessions had been held in Community P at accessible times and locations rather than in Community Q, would the Board's conclusion that Firm DBA's report was invalid and non-objective still hold?

Engineer M's Concern Expression fulfills the paramount safety obligation by surfacing a legitimate risk, but because it triggers the Firm's Concern Dismissal rather than corrective action, the ethical act is immediately undermined by the downstream chain toward a Misleading Report Submission.

Escalation to Client carries no direct fulfill or violate tag yet is guided by the public welfare obligation, and it matters because it is the necessary corrective step after the Firm's refusal at the Ethics Conference, ultimately forcing the Licensure Board Reporting Decision that restores accountability the Firm avoided.

Public Engagement Scheduling violates the paramount safety obligation because its design choices directly produce both Low Community Participation, which silences Displacement Concerns, and Supportive Comments Reception, which together feed the Misleading Report Submission that misrepresents public sentiment on a safety-relevant project.

The Outreach Method Directive itself is neutral with no fulfill or violate tag, but its normative weight comes from being the causal origin that compels the Firm to enact the scheduling choices that then violate the public safety obligation, showing how an upstream directive can seed a downstream ethical failure.

Concern Dismissal violates the paramount public safety obligation precisely because it converts a properly raised safety concern into suppressed information, directly causing the Misleading Report Submission that misinforms decision makers relying on the report's accuracy.

By omitting the community's displacement concerns while highlighting only supportive comments, the Misleading Report Submission violates truthfulness and non-omission duties, and this deception is precisely what later compels Engineer M to raise the matter in an Ethics Conference With Firm, showing how the upstream dismissal of concerns culminated in a report whose dishonesty had direct downstream consequences for professional accountability.

Engineer M's decision to confront the firm rather than silently participate in or ignore the misleading report fulfills the duty to avoid association with dishonest enterprises and to advise when a project will fail, and this action, guided by paramount concern for public welfare and ethical conduct, is what forces the escalation to the client when the firm refuses to correct course.

Because the client (City) failed to act after escalation, Engineer M's subsequent decision about whether to report to the licensure board is guided by the paramount duty to protect public safety and welfare, making this action the final safeguard against the harms that began with skewed engagement scheduling and a deceptive report.

The question arises because Engineer M Awareness Of Outreach Deficiencies places him in a position where staying silent about a report he knows is incomplete could violate honesty and public welfare obligations, yet directly challenging a peer firm's report raises questions about the limits of his authority and role.

The question arises because Engineer M sits between a client relationship and a firm-produced report with known deficiencies, creating uncertainty about which duty (client transparency versus firm loyalty) takes precedence and what form any disclosure should take.

The question arose because the deficient and selectively framed Public Engagement Report reveals conduct that looks like a Code violation, yet the entity responsible, Firm DBA, occupies an ambiguous position outside the traditional individual-engineer scope the NSPE Code was written to govern.

The question arises because Engineer M Awareness Of Outreach Deficiencies reveals two distinct wrongs, the City's discriminatory Outreach Method Directive and Firm DBA's Misleading Report Submission, forcing a determination of whether his ethical obligations extend beyond the document he was asked to assess to the client conduct that shaped it.

The question arises because Firm DBA's dismissal of legitimate concerns and proceeding with a misleading report puts Engineer M's duty of honest professional association in direct tension with obligations to attempt remediation or escalation before disengaging.

The question emerged because Firm DBA structured its outreach failures under a department not labeled 'engineering,' creating ambiguity about whether Code obligations for complete, honest, and objective reporting extend to that unit or can be organizationally evaded.

The question arises because Engineer M's awareness of outreach deficiencies and Community P's displacement exposure sit at the boundary between a contract-based obligation to the City and the Code's broader public welfare principle, leaving unresolved whether affected non-client communities are owed obligations independent of the client relationship.

The question arises because Firm DBA's report omits key details about when and where sessions were held and whether written comments were accepted, actions that fulfill the City's political and economic directive but conflict with the professional duty to issue objective, complete, and truthful engagement claims.

The question arises because Firm DBA operated under a City Directive On Engagement Sessions that shaped a deficient outreach process, and then produced a report that appears to shield that process from scrutiny, creating an unresolved conflict between the engineer's independent duty of complete and honest reporting and the firm's apparent deference to the City's business preferences and established project practices.

The question emerged because the firm's report omissions and scheduling practices raised public welfare concerns, yet the firm's defense that public relations is not engineering services creates a jurisdictional boundary dispute over whether the Code even applies.

This question arose because the same report that must objectively document a flawed public engagement process is the one that would reveal, through that same documentation, the very community harm and displacement exposure the process caused, forcing a choice between full transparency and protecting the community's dignity.

The question arose because Firm DBA's Public Engagement Report selectively presented favorable participation results while excluding facts (times, locations, comment methods) that a strict duty-based reading of the Code would deem necessary for truthful and complete disclosure, creating a direct clash between the obligation to report fully and the act of curating a report that supports a particular narrative.

The question arises because Firm DBA achieved a client favored result through Misleading Report Submission, creating a direct conflict between judging the action by its consequences and judging it by the integrity obligations it violated.

The question arises because Engineer M's concern expression satisfied an internal, character based standard of professional conduct without altering the deficient outreach process or the misleading report, leaving open whether integrity should be judged by the act of dissent itself or by its practical effect on protecting Community P.

The question arises because Engineer M sits at the intersection of a partnership relationship and a professional Code obligation, and the failed informal correction attempt removes the middle-ground option, forcing a choice between two legitimate but conflicting duties.

Because the record shows both a City-issued directive on how sessions should be run and a Firm DBA report with specific omissions and framing, it becomes contested whether the unethical conclusion attaches to Firm DBA's own professional choices or is partly attributable to the client's instructions, generating the hypothetical counterfactual question.

The question arises because Firm DBA Report Code Violation and Code Applicability To Firm DBA depend on an unstated premise, namely that licensed engineers held supervisory and ownership roles over the outreach function, and removing that premise exposes uncertainty about whether the Code's authority extends to a firm's non-technical activities.

This question arose because the case record ties the material misrepresentation charge to both an incomplete outreach process and an inaccurate characterization of community sentiment, leaving ambiguous whether curing the procedural gap (written comments) would also cure the substantive honesty violation.

This question arises because the Board's finding of invalidity conflates two distinct failures, deficient outreach location and dishonest reporting of that outreach, making it unclear whether fixing the location alone would have satisfied the objectivity and completeness obligations.

Given that Firm DBA's report omitted scheduling, location, and comment-method details material to the support claim, the board concluded Engineer M must treat the report as invalid because the omissions constitute Code violations of objectivity and truthfulness rather than mere stylistic choices.

Because Firm DBA dismissed Engineer M's concerns and proceeded with the report, the board reasoned that Engineer M's obligations escalate stepwise, first to the firm, then to the client, and finally to the licensure board, only as each prior avenue proves unsuccessful.

Given that Firm DBA's outreach work was carried out under the ownership and supervision of licensed engineers, the board concluded the Code still applies to that work despite it not being labeled 'engineering services'.

Because the City explicitly directed outreach sessions in a manner disadvantaging Community P, the board reasoned this went beyond an ordinary client preference and directed a Code violation, so Engineer M's duty to confer with the City must address the City's own culpability, not just relay the firm's failures.

Given that Firm DBA's communications and public relations department remained under the ownership and supervision of licensed engineers, the board concluded that labeling it non-engineering could not exempt its outputs from Code obligations, since doing so would create a loophole undermining the Code's intent.

Given that Engineer M's concerns were dismissed and a misleading report was submitted anyway, and that report may already influence decisions affecting Community P, the board concluded that the phased 'correct-then-report' recommendation understates that the II.1.f threshold has arguably already been met.

Because the City itself instructed scheduling that disadvantaged Community P for its own economic and political reasons, the board concluded this was a distinct client-level ethical problem that Engineer M must raise directly with the City under the paramount public welfare duty, not treat as purely an internal firm matter.

Because Firm DBA's public relations department was still owned and supervised by licensed engineers and its work directly informed the engineering report justifying the highway decision, the board concluded that departmental labeling could not shield the firm from Code accountability, since permitting such separations would create an exploitable loophole.

Given that Community P faces material displacement and disruption risk from decisions grounded in Engineer M's work, the board concluded that the absence of a direct contract does not diminish Engineer M's duty under I.1 to ensure the factual record affecting that community is honest and complete.

Because Firm DBA omitted material outreach details in deference to the City's political and economic preferences, the board concluded that such deference cannot excuse the omission, since the Code's honesty and complete reporting duties under I.3 and II.3.a remain independent of client preference.

Given that the PR department's data materially shaped the engineering report and licensed engineers controlled that department, the board concluded that Firm DBA could not use an internal organizational label to escape Code obligations that attach to the substance of the activity rather than its departmental name.

Given that Firm DBA omitted material scheduling and process details from its report, the board concluded a deontological duty violation occurred because the duty to report truthfully and completely under I.3, II.3.a, and III.3.a is categorical and not excused by the omissions failing to change the ultimate outcome or being directed by the City.

Given that Engineer M's informal attempts to correct Firm DBA failed and the violation remained undocumented as resolved, the board concluded that the II.1.f reporting duty took precedence over professional courtesy, since the Code does not permit collegial loyalty to override protection of the profession's integrity once informal correction is exhausted.

Given that the objectivity and completeness obligations attach to the engineer's own judgment rather than to client instructions, the board concluded that Firm DBA would remain independently responsible for its outreach and reporting deficiencies even in the counterfactual absence of a specific City directive.

Given that the outreach sessions were inaccessible in timing, location, and format even apart from the comment-submission gap, the board concluded that merely adding a written-comment method would likely not cure the material misrepresentation of Community P's support, since the deeper problem was systemic exclusion from participation.

Given that the City directed sessions favoring an alternate route and Firm DBA responded by omitting scheduling, location, and comment-method facts rather than refusing or disclosing them, the board concluded that client accommodation cannot justify sacrificing truthful, complete reporting under the Code.

Because licensed engineers owned and supervised the communications department and its outreach activities bore directly on community displacement risk, the board concluded that Firm DBA could not use internal departmental labels to escape Code obligations that attach to the firm as a whole.

Given that the scheduling, location, and comment-method deficiencies were facts Firm DBA could have disclosed without altering the underlying process, the board concluded that only Firm DBA's choice to hide them, not any true conflict between dignity and objectivity, produced the appearance of tension.

Should Firm DBA issue a complete and honest report of the engagement process, or submit a report that omits session logistics and claims Community P's support?

Should Engineer M challenge the validity of Firm DBA's report given its material omissions, or accept the report as issued?

When Firm DBA dismisses Engineer M's concerns, should Engineer M escalate stepwise from the firm to the City and then to the licensure board, or report to the licensure board immediately?

Should Engineer M withdraw from continued association with Firm DBA, or remain involved to pursue correction and escalation?

Should Firm DBA's licensed engineer principals treat the communications and public relations department's outreach work as governed by the NSPE Code, or as exempt because it is not labeled engineering services?

Should Engineer M treat the City's directive to schedule outreach sessions disadvantaging Community P as a separate ethical issue requiring direct engagement with the City, or address it only through correcting Firm DBA's report?