Step 4: Review

Act for each employer or client as faithful agents or trustees.

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

Engineers shall conform with state registration laws in the practice of engineering.

The Board cited this case to illustrate the ethical obligation of an engineer who discovers a potential violation by a colleague to first communicate directly with that colleague before reporting to authorities, balancing collegial responsibility with public safety duties.

Engineer A should communicate with Engineer X to obtain clarification regarding the matter in question.

If Engineer A is not sufficiently satisfied with Engineer X's explanation, Engineer A may be required to report this matter to the state engineering licensure board.

Before initiating collegial contact with Engineer X, Engineer A bears an affirmative epistemic duty to independently verify XYZ Engineering's certificate of authority status through available public records maintained by the State P licensure board. The Board's recommendation to communicate with Engineer X presupposes that Engineer A's belief in the violation is reasonably grounded, not merely speculative or competitively motivated. If Engineer A proceeds to collegial contact - or worse, to formal reporting - on the basis of unverified suspicion, and it subsequently emerges that XYZ Engineering did in fact hold a valid certificate of authority, Engineer A would face serious exposure under Code provision III.7, which prohibits malicious or false injury to a competitor's professional reputation. The verification step is therefore not merely procedurally courteous; it is a threshold ethical obligation that protects Engineer X's rights, preserves Engineer A's own integrity, and ensures that the reporting mechanism is not weaponized through competitive animus. The standard of certainty required is not absolute proof, but it must be sufficient to constitute a reasonable professional judgment - meaning Engineer A should have consulted publicly accessible licensure records and found no certificate of authority on file before treating the matter as a confirmed violation warranting any further action.

The Board's graduated sequence - collegial contact first, formal report only if Engineer A remains unsatisfied - implicitly assumes that Engineer A can engage in collegial outreach with motivational integrity despite being a direct competitor who previously served Client L. This assumption deserves explicit scrutiny that the Board did not provide. Engineer A's structural position creates a dual-motivation problem: the same act of reporting simultaneously advances Engineer A's legitimate professional duty and Engineer A's competitive business interest in recovering or retaining Client L's business. Because these motivations are inseparable in outcome, Engineer A cannot resolve the conflict simply by asserting good faith. Instead, Engineer A should apply heightened self-scrutiny at each decision point - asking not only whether a violation appears to exist, but whether the urgency, framing, and sequencing of Engineer A's response would be identical if Engineer X were not a competitor for Client L's work. If Engineer A cannot honestly answer that question affirmatively, the collegial contact should be conducted with particular care to avoid any language that could be construed as leveraging the regulatory situation for competitive advantage, and Engineer A should document the basis for each step taken to demonstrate that the reporting process was driven by professional duty rather than business interest. The Board's framework is sound, but its application requires Engineer A to exercise a degree of self-monitoring that the Board left unstated.

The Board's recommendation that Engineer A 'may be required' to report to the State P licensure board if unsatisfied with Engineer X's explanation understates the conditionality and clarifies too little about what 'sufficiently satisfied' means in practice. The Board's language implies that formal reporting remains discretionary even after collegial contact fails to resolve the matter, but this reading is difficult to reconcile with Code provision II.1.f, which imposes a reporting obligation on engineers who have knowledge of alleged violations. Once Engineer A has verified the non-compliance and received an explanation from Engineer X that does not establish that XYZ Engineering has obtained or is imminently obtaining a certificate of authority, the violation is no longer merely alleged - it is confirmed and ongoing. At that point, Engineer A's obligation to report to the State P licensure board becomes substantially less discretionary and more mandatory. The word 'may' in the Board's conclusion should therefore be understood as reflecting the contingency of the factual predicate - i.e., whether Engineer X's explanation resolves the matter - rather than as granting Engineer A ongoing discretion to decline reporting once the violation is confirmed. Particularly where the unauthorized practice is willful or continues after collegial notice, the professional reciprocity norm cannot be stretched to justify indefinite forbearance, because doing so would allow ongoing unlicensed practice to harm the public and undermine the licensure system that protects it.

The Board's analysis is silent on Engineer A's obligations toward Client L, yet the facts present a distinct ethical dimension that the Board's two conclusions do not address. Client L is currently receiving engineering services from a firm that lacks a certificate of authority to practice in State P, which means Client L may be exposed to legal, contractual, and safety risks arising from that non-compliance - including the possibility that engineering work product produced without proper authorization may be unenforceable, uninsured, or subject to regulatory challenge. While Engineer A's primary reporting obligation runs to the State P licensure board, Code provision I.4 - requiring engineers to act as faithful agents or trustees - and the broader public welfare mandate embedded in the Code suggest that Engineer A has at minimum a duty to consider whether Client L should be made aware of the situation. However, this consideration must be handled with extreme care: proactively contacting Client L to inform it of XYZ Engineering's non-compliance would be ethically permissible only if done in a manner that is factually accurate, professionally measured, and not designed to solicit Client L's business for ABC Engineering. If Engineer A's communication with Client L were framed or timed in a way that exploited the regulatory situation to recover a lost client, it would cross from professional duty into the kind of competitive conduct that Code provision III.7 is designed to prohibit. The Board's silence on this dimension leaves Engineer A without guidance on a genuinely difficult question, and the safest course is for Engineer A to focus on the collegial and regulatory channels the Board identified, rather than independently notifying Client L.

The Board's graduated reporting framework - collegial contact preceding formal regulatory report - draws implicit support from the analogous structure established in BER Case 96-8, where a reviewing engineer was directed to discuss safety findings with the engineer under review before escalating to authorities. However, the analogy has a critical limit that the Board did not articulate: in BER 96-8, the confidentiality agreement governing the peer review relationship created a genuine competing obligation that justified a deliberate, sequenced approach. In the present case, no such confidentiality obligation exists between Engineer A and Engineer X. The collegial-first sequence here is grounded not in a competing duty of confidentiality but in professional courtesy, the possibility of inadvertent non-compliance, and the risk that Engineer A's competitive interest might distort a premature formal report. These are legitimate but weaker justifications for delay than those present in BER 96-8. Consequently, the window for collegial resolution in the present case should be understood as narrower and less tolerant of prolonged forbearance than the BER 96-8 framework might suggest. If Engineer X does not respond promptly to collegial contact, or responds in a manner that confirms the violation without committing to immediate remediation, Engineer A's obligation to report to the State P board should be treated as triggered without further delay. The cross-case analogy is instructive but should not be read to import BER 96-8's more extended deliberative tolerance into a context where no confidentiality constraint justifies it.

In response to Q101, Engineer A does bear an affirmative duty to verify XYZ Engineering's certificate of authority status before treating the matter as a confirmed violation warranting either collegial contact or formal reporting. The epistemic threshold required, however, is not absolute certainty but rather reasonable professional confidence - meaning Engineer A must make a good-faith inquiry into publicly available licensure records in State P, which are typically accessible through the state engineering licensure board's online registry. If those records confirm the absence of a certificate of authority, Engineer A has satisfied the verification obligation and may proceed to collegial contact. Engineer A is not required to conduct an exhaustive investigation or to give Engineer X advance notice before verifying the public record. The verification obligation exists primarily to protect Engineer X from a report grounded in error or assumption, and to protect Engineer A from the professional and ethical consequences of a false or malicious report under Code provision III.7. Once publicly available records confirm non-compliance, the epistemic threshold is met and Engineer A's subsequent obligations are triggered.

In response to Q102, Engineer A's status as a direct competitor of Engineer X - and specifically as the firm that previously served Client L - creates a structural conflict of interest that does not eliminate Engineer A's reporting obligations but does impose a heightened duty of self-scrutiny throughout the decision-making process. The conflict is structural rather than merely incidental because Engineer A stands to benefit materially if XYZ Engineering is removed from the State P market or loses the Client L engagement. This benefit is not hypothetical: it is the direct consequence of a successful report. The ethical framework does not permit Engineer A to suppress the reporting duty on account of competitive motivation, nor does it permit Engineer A to weaponize the reporting mechanism as a competitive tool. The resolution lies in procedural discipline: Engineer A must verify the violation through objective public records rather than assumption, must approach collegial contact with genuine corrective intent rather than as a performative step before an inevitable report, and must examine whether the urgency and framing of any formal report reflects the public interest rather than competitive advantage. The Board's graduated sequence - collegial contact first, formal report only if unsatisfied - is itself a structural safeguard against competitive misuse of the reporting mechanism, because it creates a record of good-faith corrective engagement before escalation.

In response to Q103, the distinction between inadvertent and willful non-compliance by XYZ Engineering is ethically significant and should affect both the sequencing and the urgency of Engineer A's reporting obligations, though it does not eliminate those obligations in either case. Where non-compliance appears inadvertent - for example, where Engineer X is unaware of State P's certificate of authority requirement or has simply failed to complete the administrative process - the collegial-first approach prescribed by the Board is not only appropriate but ethically required, because it gives Engineer X a meaningful opportunity to cure the violation before formal regulatory consequences attach. The public interest is adequately served by prompt correction, and the profession's interest in collegial self-regulation supports this approach. Where, however, Engineer A has reason to believe the non-compliance is willful - for example, where Engineer X has previously been informed of the requirement and has continued practice without compliance, or where Engineer X explicitly acknowledges the deficiency and refuses to remedy it - the collegial step either collapses into futility or has already been effectively completed. In that circumstance, Engineer A's obligation to report to the State P licensure board becomes more immediate and less discretionary, because the public welfare rationale for graduated response is undermined when the violating party has demonstrated deliberate disregard for jurisdictional licensure requirements. The inadvertent-versus-willful distinction therefore functions as a variable that calibrates the weight Engineer A should give to the collegial step relative to the formal reporting obligation.

In response to Q104, Engineer A's ethical obligations toward Client L are more constrained than they might initially appear. The NSPE Code's public welfare provisions create a general duty to protect the public from engineering practice that does not meet jurisdictional requirements, but this duty does not straightforwardly translate into an affirmative obligation for Engineer A to proactively contact Client L and inform them of XYZ Engineering's non-compliance. Several considerations counsel restraint: first, Client L is a former client, not a current one, so Engineer A's fiduciary duty as a faithful agent under Code provision I.4 does not directly apply to this relationship. Second, proactive disclosure to Client L - particularly given Engineer A's competitive interest in recovering that client relationship - risks crossing the line from public welfare protection into conduct that maliciously or falsely injures a competitor's professional reputation under Code provision III.7, especially if the violation is inadvertent and potentially curable. Third, the appropriate mechanism for protecting Client L and the public is the licensure board, not a direct communication from a competitor. Engineer A's obligation to Client L is therefore best discharged indirectly: by following the Board's graduated reporting sequence, which, if it results in a formal report to the State P licensure board, will trigger the regulatory process designed to protect clients and the public from unlicensed practice. Direct contact with Client L by Engineer A would be ethically problematic unless Engineer A had independent reason to believe that Client L faced imminent safety risk from the unlicensed engagement - a circumstance not established by the facts as presented.

In response to Q201, the tension between the Collegial Pre-Reporting Engagement principle and the Mandatory Reporting Obligation principle is real and is sharpened - though not resolved differently - by Engineer A's competitive interest. The risk that collegial outreach functions as a delay tactic rather than a genuine corrective mechanism is not merely theoretical: Engineer A could use the collegial contact phase to gather information about XYZ Engineering's client relationships, to signal to Client L that XYZ Engineering is non-compliant, or simply to extend the period during which XYZ Engineering is exposed to regulatory risk. The ethical resolution requires that Engineer A treat the collegial contact phase as time-bounded and purpose-specific. Its purpose is to give Engineer X a genuine opportunity to cure the violation or to provide information that changes Engineer A's assessment of whether a violation has occurred. It is not an open-ended deliberative period. If Engineer X responds promptly and demonstrates that corrective action is underway, Engineer A's obligation to report is substantially reduced. If Engineer X is unresponsive, dismissive, or continues practice without remediation, the collegial phase has served its purpose and Engineer A's reporting obligation becomes operative without further delay. The competitive interest does not change this sequencing but does require Engineer A to be especially vigilant that the collegial phase is not being unconsciously extended or instrumentalized in ways that serve competitive rather than corrective ends.

In response to Q301 and Q304 considered together from a deontological perspective, Engineer A does not have an unconditional duty to report immediately to the State P licensure board, but does have a categorical duty to ensure that the epistemic verification obligation does not become a procedural mechanism for indefinite delay. Deontological analysis under a Kantian framework would hold that Engineer A's duty to report unauthorized practice is grounded in the universalizability of the rule that engineers must uphold licensure integrity - a rule that cannot be suspended merely because the reporter has a competitive interest in the outcome. However, the same framework's requirement of fairness to Engineer X as a rational agent entitled to due consideration supports the verification obligation: Engineer A must not report on the basis of assumption or incomplete information, because doing so would treat Engineer X as a means to Engineer A's competitive ends rather than as a professional peer entitled to accurate treatment. The deontological resolution is therefore that the verification obligation is a genuine duty of fairness, not a loophole - but it must be discharged promptly and in good faith. Once verification is complete and collegial contact has been attempted without satisfactory resolution, the duty to report becomes categorical and is not diminished by Engineer A's competitive interest, because the duty's foundation is the integrity of the licensure system and the protection of the public, not the purity of Engineer A's motivation.

In response to Q302, the collegial-first approach prescribed by the Board does reflect the disposition of a professionally virtuous engineer when applied in good faith, but it carries a genuine virtue ethics risk that Engineer A's competitive self-interest masquerades as professional courtesy. Virtue ethics analysis focuses on the character of the agent and the integrity of the motivational structure behind the action, not merely on whether the action conforms to a prescribed sequence. An engineer of genuinely virtuous character would approach the collegial contact with Engineer X from a disposition of professional solidarity - a sincere desire to give a colleague the opportunity to correct an inadvertent error - rather than from a disposition of competitive calculation. The risk is that Engineer A, operating in a context of competitive motivation, performs the collegial contact as a procedural formality while internally treating it as a step toward a predetermined outcome of formal reporting that will benefit ABC Engineering. The virtue ethics framework would require Engineer A to engage in honest self-examination about the motivational structure of the collegial contact: Is Engineer A genuinely open to being persuaded that no violation has occurred, or that the violation is being remedied? Is Engineer A prepared to forgo formal reporting if Engineer X provides a satisfactory explanation? If the answer to these questions is no - if the collegial contact is a performance rather than a genuine engagement - then the Board's prescribed sequence, while procedurally followed, is not being executed with the virtuous character it presupposes.

In response to Q303, the Board's graduated reporting sequence - collegial contact first, formal report only if unsatisfied - produces better aggregate outcomes for public welfare, licensure system integrity, and professional trust than an immediate mandatory report would, for several interconnected reasons. From a consequentialist perspective, the relevant outcomes include not only the specific case of XYZ Engineering's compliance but also the systemic effects on how engineers across the profession respond to discovered violations. A regime of immediate mandatory reporting without collegial engagement would likely produce a higher rate of reports grounded in error or assumption, would damage professional relationships and trust, and would impose disproportionate regulatory burdens on licensure boards that must investigate every report regardless of whether the violation was inadvertent and self-correcting. The graduated sequence, by contrast, filters out cases where the violation is inadvertent and promptly remedied - which are likely the majority of certificate of authority cases - while preserving the formal reporting mechanism for cases where collegial engagement fails. The public welfare is served because the ultimate outcome in non-compliant cases is the same: either Engineer X obtains the certificate of authority, or the matter is reported to the licensure board. The licensure system's integrity is served because the board's investigative resources are directed toward cases that genuinely require regulatory intervention. Professional trust is served because the collegial mechanism demonstrates that the profession takes self-regulation seriously without treating every administrative deficiency as a matter requiring immediate formal sanction. The one consequentialist risk of the graduated sequence - that it allows ongoing unlicensed practice during the collegial engagement period - is real but is mitigated by the time-bounded nature of the collegial phase and by the fact that certificate of authority violations, while serious, typically do not present the same immediacy of public safety risk as, for example, structural engineering errors.

In response to Q401, if Engineer A had no prior business relationship with Client L and no competitive stake in XYZ Engineering's engagement, the Board's ethical analysis and reporting sequence would likely remain structurally identical - the graduated approach of collegial contact followed by formal reporting if unsatisfied is grounded in the nature of the violation and the profession's self-regulatory norms, not in the reporter's competitive status. However, the presence of competitive motivation does not merely require heightened self-scrutiny as a procedural add-on; it structurally alters the ethical texture of Engineer A's obligations in at least two ways. First, it introduces a duty of motivational transparency that would not exist for a disinterested reporter: Engineer A must be prepared to examine and, if asked, to account for the fact that the report serves competitive as well as public interest ends. Second, it raises the threshold of care Engineer A must apply to the verification obligation, because the consequences of a mistaken or premature report fall not only on Engineer X but also on the integrity of Engineer A's own professional standing. A disinterested reporter who makes a good-faith error in verification faces primarily the consequence of having caused an unnecessary investigation; Engineer A, as a competitor, faces the additional consequence of having potentially violated Code provision III.7 by injuring a competitor's professional reputation through a false report. The competitive relationship therefore does not change the sequence of obligations but does increase the ethical stakes attached to each step in that sequence.

In response to Q402, if Engineer X, upon collegial contact by Engineer A, acknowledged the missing certificate of authority but continued providing engineering services in State P while claiming the application was pending, Engineer A's obligation to report to the State P licensure board would become substantially more immediate and considerably less discretionary, though the analysis requires nuance. The acknowledgment of the deficiency combined with continued practice eliminates the possibility that the violation is based on Engineer X's ignorance of the requirement - the inadvertence rationale for the collegial-first approach no longer applies. The claim that an application is pending is a mitigating factor but not a dispositive one: a pending application does not confer the legal authority to practice, and Engineer X's continuation of services during the pendency of the application means that the public and Client L remain exposed to the risks that the certificate of authority requirement is designed to prevent. In this circumstance, Engineer A should report to the State P licensure board, because the collegial engagement has run its course - Engineer X has been informed, has acknowledged the deficiency, and has chosen to continue practice rather than suspend it pending compliance. The report at this stage is not premature or competitive in character; it is the appropriate escalation that the Board's graduated framework contemplates when collegial engagement does not produce corrective action. Engineer A should document the collegial exchange to demonstrate that the reporting sequence was followed in good faith.

In response to Q404, if Engineer A had immediately reported XYZ Engineering to the State P licensure board without first contacting Engineer X, and it subsequently emerged that XYZ Engineering had in fact obtained a certificate of authority that Engineer A had simply failed to verify, Engineer A would face significant ethical exposure under Code provision III.7, which prohibits engineers from attempting to injure, maliciously or falsely, directly or indirectly, the professional reputation of another engineer. The critical question would be whether Engineer A's failure to verify constituted a false report within the meaning of that provision. If Engineer A had access to publicly available licensure records and failed to consult them before reporting - particularly given Engineer A's competitive interest in the outcome - the failure to verify would be difficult to characterize as a good-faith error. The competitive context transforms what might otherwise be an innocent oversight into conduct that at minimum raises the inference of reckless disregard for Engineer X's professional reputation. Engineer A could also face consequences under the state licensing board's rules of professional conduct, which in many jurisdictions treat false or misleading statements to regulatory authorities as independent grounds for disciplinary action. This counterfactual powerfully illustrates why the epistemic verification obligation is not merely a procedural nicety but a substantive ethical requirement: it is the mechanism by which Engineer A demonstrates that the report is grounded in fact and public interest rather than competitive motivation, and its omission - especially by a competitor - exposes Engineer A to the very type of professional misconduct charge that Code provision III.7 is designed to prevent.

The central principle tension in this case - between Collegial Pre-Reporting Engagement and Mandatory Reporting Obligation - is resolved not by subordinating one to the other but by sequencing them. The Board treats collegial contact as a procedural precondition to formal reporting, not as an alternative to it. This sequencing reflects a broader principle prioritization logic: where a violation may be inadvertent and correctable without regulatory intervention, the profession's interest in self-governance through peer correction takes temporary precedence over the state's interest in immediate enforcement. However, this priority is strictly conditional and time-limited. Once collegial engagement fails to produce a satisfactory explanation or remediation, the Mandatory Reporting Obligation reasserts itself with full force and is not further defeatable by appeals to professional courtesy or competitive neutrality. The case thus teaches that Collegial Pre-Reporting Engagement is a duty-modifying principle - it shapes how and when the reporting duty is discharged - but it cannot extinguish the underlying reporting obligation. The sequencing is not a loophole; it is a structured pathway that preserves both professional reciprocity and licensure integrity.

The most structurally complex principle tension in this case is the conflict between Competitive Motivation Scrutiny and the Epistemic Verification Obligation. Engineer A's competitive interest in the outcome - as the firm that previously served Client L and now stands to benefit if XYZ Engineering is removed from the State P market - creates a genuine risk that the threshold of certainty Engineer A applies before concluding a violation has occurred will be biased downward by self-interest. The Epistemic Verification Obligation principle demands that Engineer A confirm XYZ Engineering's non-compliance status before initiating either collegial contact or formal reporting, precisely because acting on unverified information against a competitor could constitute the kind of malicious or false injury to professional reputation prohibited under Code provision III.7. The resolution the Board implicitly adopts is that these two principles are mutually reinforcing rather than conflicting: the competitive motivation scrutiny obligation requires Engineer A to apply a higher standard of epistemic care, not a lower one, before acting. This means Engineer A must affirmatively verify the certificate of authority status through available public records or direct inquiry before treating the matter as a confirmed violation. The case teaches that when competitive interest is present, the verification threshold rises - competitive motivation does not license faster action; it demands more careful action.

The Engineering Business-Profession Duality principle - which acknowledges that Engineer A simultaneously holds legitimate competitive interests and professional regulatory obligations - cannot be resolved by cleanly separating self-interested from duty-driven motivation, because in this case both motivations point toward the same action: reporting XYZ Engineering's non-compliance. The Board's framework implicitly accepts this motivational entanglement as ethically tolerable provided that Engineer A's conduct satisfies the procedural and epistemic standards the Code imposes independently of motivation. This reflects a deontologically significant insight: the ethical validity of Engineer A's reporting obligation does not depend on the purity of Engineer A's motivation, but on whether the action is taken in conformity with the Code's prescribed sequence - verification, collegial contact, and formal report only if necessary. The Licensure Integrity principle and the Jurisdiction-Specific Compliance Violation principle together establish that the public interest in enforcing certificate of authority requirements is a sufficient independent justification for reporting, regardless of whether Engineer A also benefits competitively. The case therefore teaches that mixed-motive reporting is ethically permissible when the underlying duty is genuine, the procedural sequence is followed, and the epistemic standard is met - but that the presence of competitive motivation imposes a continuing self-scrutiny obligation on Engineer A throughout the process to ensure that competitive interest does not distort the timing, framing, or escalation of the report.

What are Engineer A’s ethical obligations under these facts?

Does Engineer A have an affirmative duty to verify XYZ Engineering's certificate of authority status before concluding a violation has occurred, and if so, what level of epistemic certainty is required before initiating either collegial contact or formal reporting?

To what extent does Engineer A's status as a direct competitor of Engineer X - and as the firm that previously served Client L - create a structural conflict of interest that should require Engineer A to apply heightened self-scrutiny before deciding whether and how to report the certificate of authority violation?

Does the ethical framework change if Engineer A has reason to believe that XYZ Engineering's lack of a certificate of authority is willful rather than inadvertent, and should the distinction between inadvertent and deliberate non-compliance affect the sequencing or urgency of Engineer A's reporting obligations?

What obligation, if any, does Engineer A have toward Client L - a former client now potentially receiving engineering services from an unlicensed firm - and does Engineer A's duty to protect the public extend to proactively informing Client L of XYZ Engineering's non-compliance?

Does the Collegial Pre-Reporting Engagement principle conflict with the Mandatory Reporting Obligation principle when Engineer A's competitive interest in the outcome creates a risk that collegial outreach is used as a delay tactic rather than a genuine corrective mechanism - and if so, how should Engineer A resolve this tension?

Does the Competitive Fairness Dimension of XYZ Engineering's Unauthorized Practice - which benefits Engineer A if XYZ is removed from competition - conflict with the Epistemic Verification Obligation principle, in that Engineer A's competitive interest may bias the threshold of certainty Engineer A applies before concluding a violation has occurred and acting on it?

Does the Licensure Integrity principle - which demands that unauthorized practice be reported to protect the profession and the public - conflict with the Professional Reciprocity Norm when Engineer A must decide how much latitude to extend to Engineer X before escalating to formal reporting, given that excessive deference to reciprocity could allow ongoing unlicensed practice to harm the public?

Does the Engineering Business-Profession Duality principle - which acknowledges Engineer A's legitimate competitive interests - conflict with the Jurisdiction-Specific Compliance Violation principle when Engineer A must decide whether to report, given that the same act of reporting simultaneously serves Engineer A's business interest and the profession's regulatory integrity, making it impossible to cleanly separate self-interested from duty-driven motivation?

From a deontological perspective, does Engineer A have an unconditional duty to report XYZ Engineering's lack of a certificate of authority to the State P licensure board, regardless of whether Engineer A's competitive interest in the matter might taint the motivation behind the report?

From a virtue ethics standpoint, does the collegial-first approach prescribed by the Board reflect the disposition of a professionally virtuous engineer, or does it risk allowing Engineer A's competitive self-interest to masquerade as professional courtesy, thereby undermining the integrity of the reporting process?

From a consequentialist perspective, does the Board's graduated reporting sequence - collegial contact first, formal report only if unsatisfied - produce better outcomes for public welfare, licensure system integrity, and professional trust than an immediate mandatory report to the State P board would?

From a deontological perspective, does the epistemic verification obligation - requiring Engineer A to confirm XYZ Engineering's non-compliance before reporting - represent a genuine duty of fairness owed to Engineer X, or does it create a procedural loophole that allows unauthorized practice to continue unchecked while Engineer A deliberates?

If Engineer A had no prior business relationship with Client L - and therefore had no competitive stake in XYZ Engineering's engagement - would the Board's ethical analysis and reporting sequence have differed, and does the presence of competitive motivation structurally alter Engineer A's obligations or merely require heightened self-scrutiny?

What if Engineer X, upon being contacted collegially by Engineer A, acknowledged the missing certificate of authority but continued providing engineering services in State P while claiming the application was pending - would Engineer A's obligation to report to the State P licensure board become immediate and unconditional at that point?

If the BER 96-8 peer review precedent had established that confidentiality obligations fully override reporting duties even in cases of safety violations, how would that alternative precedent have affected the graduated reporting framework the Board applied to Engineer A's certificate of authority discovery?

What if Engineer A had immediately reported XYZ Engineering to the State P licensure board without first contacting Engineer X, and it subsequently emerged that XYZ Engineering had in fact obtained a certificate of authority that Engineer A had simply failed to verify - what ethical and professional consequences would Engineer A face under Code provisions governing malicious or false injury to a competitor's professional reputation?

Engineer X's acceptance of an engagement in State P without obtaining a certificate of authority directly violates the jurisdictional pre-practice compliance obligation and undermines licensure integrity, triggering Engineer A's discovery and subsequent ethical decision-making obligations.

Engineer A's deliberation about how to respond to the discovered violation is the central ethical decision point, requiring simultaneous satisfaction of epistemic verification, competitive motivation scrutiny, collegial priority sequencing, and jurisdiction-specific reporting threshold obligations before any formal or informal action is taken.

Directly contacting Engineer X fulfills the collegial pre-reporting engagement obligation by giving Engineer X the opportunity to remedy an apparently inadvertent certificate of authority violation before formal board reporting, consistent with the professional reciprocity principle and the graduated duty standard endorsed by BER precedent.

Reporting the violation to authorities ultimately fulfills the mandatory unlicensed practice reporting obligation and preserves licensure system integrity, but if done before collegial contact and epistemic verification, it violates the graduated-duty and collegial-priority constraints that condition when and how formal reporting is ethically permissible.

Obtaining the certificate of authority is the remedial action that directly fulfills Engineer X's pre-practice compliance obligation under State P law, resolves the discovered violation, and is the outcome that Engineer A's collegial contact is intended to prompt before escalation to formal board reporting.

This foundational question emerged because the discovery of a competitor's regulatory non-compliance at the moment of a former-client relationship transfer activates at least three overlapping ethical frameworks - public protection, collegial professionalism, and competitive fairness - none of which alone resolves what Engineer A must do first. The question is irreducible because each framework authorizes a different initial action and the facts do not clearly privilege one warrant over the others.

This question emerged because the Toulmin warrant authorizing the move from 'Engineer A knows of a violation' to 'Engineer A must report' depends entirely on what 'knows' means epistemically, and the facts do not specify whether Engineer A has verified XYZ Engineering's certificate status through official State P records or is relying on inference. The gap between suspicion and verified knowledge is the precise point at which the argument structure becomes contested, generating the question.

This question emerged because the data - Engineer A discovering a competitor's violation immediately after losing a client to that competitor - creates a structural coincidence that contaminates the warrant structure: the same facts that authorize reporting also raise the rebuttal that reporting is self-interested. The question is irreducible because no external fact can distinguish a legitimately motivated report from a competitively motivated one when the reporter is also the injured competitor.

This question emerged because the Toulmin warrant structure for Engineer A's reporting obligation contains an embedded intent-sensitivity: the same data point (violation discovered) leads to different conclusions depending on a mental-state variable (inadvertent vs. willful) that is not observable from the outside. The question arose because the ethical framework bifurcates on a factual distinction that Engineer A cannot resolve with available information, creating genuine normative uncertainty about sequencing and urgency.

This question emerged because Client L occupies a dual role in the ethical structure - simultaneously a member of the public whom Engineer A has a general duty to protect and a former client now retained by a competitor whom Engineer A has a specific duty not to solicit or disparage - and the facts do not resolve which role is ethically dominant. The question arose because the data (client relationship transferred to an unlicensed firm) activates two warrants that authorize opposite actions toward the same person, and no higher-order rule in the available framework clearly resolves the conflict.

This question arose because the same data event - Engineer A discovering XYZ's non-compliance while holding a competitive stake in XYZ's market exit - simultaneously triggers two warrants that prescribe opposite sequencing: one requiring collegial engagement first, one requiring reporting regardless of motivation. The question crystallizes at the intersection of these warrants because Engineer A's competitive interest is precisely the rebuttal condition that destabilizes the collegial-first warrant, making it impossible to determine whether pre-reporting engagement is ethically mandated or ethically suspect without resolving whose interest the delay serves.

This question emerged because the data - Engineer A losing Client L to XYZ and then discovering XYZ's non-compliance - creates a structural conflict between two epistemic warrants: one that authorizes Engineer A to act on the competitive fairness dimension of the violation, and one that demands that his competitive interest not contaminate the evidentiary standard he applies before concluding the violation is real and reportable. The question is irreducible because the same facts that give Engineer A standing to report (competitive harm from unlicensed practice) are the facts that most compromise his ability to assess the violation impartially.

This question arose because the data - XYZ's ongoing unauthorized practice in State P - places Engineer A at the intersection of two warrants that prescribe different amounts of latitude: the Licensure Integrity principle demands timely escalation to protect the public, while the Professional Reciprocity Norm demands that Engineer A treat Engineer X as he would wish to be treated, which implies meaningful pre-reporting engagement. The question is irreducible because the rebuttal condition (ongoing public harm from continued unlicensed practice) is precisely what determines how much reciprocity latitude is ethically permissible, and that determination cannot be made without first resolving the priority ordering of the two warrants.

This question arose because the data - Engineer A discovering XYZ's non-compliance in the same market where XYZ displaced him - makes it structurally impossible to separate the professional reporting obligation from the competitive benefit that reporting would produce, activating both the Business-Profession Duality warrant (which permits the alignment) and the Jurisdiction-Specific Compliance warrant (which demands motivational purity). The question is irreducible because the very feature that makes Engineer A's report professionally legitimate (his knowledge of the violation) is inseparable from the feature that makes his motivation suspect (his competitive stake in the outcome).

This question arose because the deontological framing of the reporting obligation - which strips motivation from the duty calculus - collides with the structural reality that Engineer A's competitive interest is not merely a background condition but a causally relevant feature of how and why the violation came to his attention, activating the Competitive Motivation Scrutiny warrant as a challenge to whether a deontological duty can be unconditionally affirmed when the agent's self-interest is woven into the very epistemic pathway that generated the duty. The question is irreducible because deontological ethics must either hold that motivation is categorically irrelevant to duty (preserving the unconditional report obligation) or acknowledge that the moral quality of duty-fulfillment is degraded by compromised motivation (qualifying the unconditional claim).

This question arose because the Board's prescribed sequence - collegial contact before formal report - is structurally indistinguishable in outward behavior from a competitor strategically managing a rival's regulatory exposure for business gain, making it impossible to evaluate the prescription's virtue-ethical validity without interrogating Engineer A's internal motivational state. The question is irreducible because virtue ethics demands that the right act be performed for the right reason, and the competitive context permanently contaminates the motivational transparency that collegial restraint requires to count as virtuous.

This question arose because the Board's graduated sequence embeds a consequentialist assumption - that collegial correction produces better outcomes than immediate formal reporting - without empirically establishing that the collegial phase actually accelerates compliance rather than merely deferring accountability. The question is structurally necessary because consequentialism requires outcome comparison across the full causal chain, and the Board's analysis stops at the first-order benefit of professional dialogue without accounting for the second-order costs of continued unauthorized practice during the deliberation window.

This question arose because the Board's requirement that Engineer A confirm non-compliance before reporting introduces a verification threshold that is deontologically ambiguous: it can be read either as a genuine duty of fairness owed to Engineer X as a fellow professional, or as a procedural delay mechanism that subordinates the public's right to licensure enforcement to Engineer A's epistemic comfort. The question is irreducible because deontological ethics requires that procedural duties be grounded in genuine moral obligations rather than serving as convenient deferrals, and the verification requirement's moral status depends entirely on whether it protects Engineer X's rights or merely delays the enforcement of Engineer A's independent duty.

This question arose because the Board's analysis acknowledges Engineer A's competitive stake but does not resolve whether that stake modifies the structure of Engineer A's obligations or merely requires internal self-monitoring, leaving open the foundational question of whether competitive motivation is ethically relevant to the existence, timing, or procedural requirements of the reporting duty. The counterfactual framing - what if Engineer A had no competitive stake - is necessary precisely because the Board's reasoning conflates the question of whether Engineer A must report with the question of whether Engineer A's motivation contaminates the report, and these are analytically distinct issues that require separate resolution.

This question arose because the Board's graduated sequence is calibrated to inadvertent violations, but the scenario describes a post-notification state in which Engineer X's continued practice can no longer be characterized as inadvertent, creating a gap in the Board's framework that requires resolution of whether the collegial-first obligation has a defined termination condition triggered by Engineer X's knowing non-compliance. The question is structurally necessary because the entire moral justification for the graduated sequence - professional reciprocity and fairness to an engineer who did not knowingly violate the law - collapses the moment Engineer X acknowledges the violation and continues anyway, and the Board's analysis does not specify what Engineer A's obligations become at that inflection point.

This question emerged because BER 96-8 established the foundational warrant hierarchy that the Board analogically transferred to Engineer A's certificate of authority situation, making the counterfactual precedent directly relevant to understanding why the graduated framework exists at all. The question surfaces the structural dependency between the peer review confidentiality-safety tension and the collegial-then-formal reporting sequence applied to unlicensed practice discovery, exposing how a different BER 96-8 outcome would have destabilized the entire obligation architecture Engineer A operated within.

This question emerged because the ethical framework governing Engineer A's reporting decision contains an internal tension between the duty to report unlicensed practice and the duty to verify facts before making claims that could injure a competitor's reputation, and the hypothetical scenario deliberately places Engineer A on the wrong side of that verification threshold. The question forces examination of what professional consequences attach when a procedurally deficient report - one that bypassed both collegial notification and epistemic verification - turns out to be factually incorrect, implicating Code provisions on false injury to competitors that would otherwise remain dormant in a straightforward unlicensed practice case.

The Board concluded that the graduated reporting sequence remains sound even when Engineer A is a competitor, but that its application requires Engineer A to exercise explicit self-scrutiny - asking whether the urgency, framing, and sequencing of each step would be identical absent competitive interest - and to document each step to demonstrate that professional duty, not business interest, drove the process. The Board reached this conclusion by recognizing that the dual-motivation problem is structural and cannot be resolved by good-faith assertion alone, necessitating a procedural discipline that the Board's original framework left unstated.

The Board concluded that the word 'may' in Conclusion_2 reflects the contingency of the factual predicate (i.e., whether Engineer X's explanation resolves the matter) rather than granting Engineer A ongoing discretion to decline reporting once the violation is confirmed. The Board reached this conclusion by reading II.1.f as substantially mandatory once knowledge of a confirmed, ongoing violation exists, and by recognizing that professional reciprocity cannot be stretched to permit indefinite forbearance where public protection and licensure integrity are at stake.

The Board concluded that Engineer A's first obligation is to communicate directly with Engineer X to obtain clarification, reflecting the profession's preference for collegial resolution before formal regulatory escalation. The Board reached this conclusion by treating the alleged violation as not yet confirmed and by applying the principle that professional peers should be afforded an opportunity to explain or remedy apparent non-compliance before a formal report is filed.

The Board concluded that if Engineer A is not sufficiently satisfied with Engineer X's explanation, Engineer A may be required to report the matter to the State P licensure board, establishing formal reporting as the mandatory backstop to the collegial engagement step. The Board reached this conclusion by grounding the escalation trigger in II.1.f's reporting obligation while preserving the conditionality of that obligation on the outcome of the prior collegial contact.

The Board concluded that Engineer A bears an affirmative epistemic duty to independently verify XYZ Engineering's certificate of authority status through publicly accessible licensure records before initiating either collegial contact or formal reporting, with the required standard being reasonable professional judgment rather than absolute proof. The Board reached this conclusion by recognizing that proceeding on unverified suspicion - particularly where competitive motivation exists - exposes Engineer A to liability under III.7 and risks weaponizing the reporting mechanism against a competitor who may in fact be compliant.

The Board - through the conclusion's own analysis filling the Board's silence - determined that while Engineer A has a conceptual duty under I.4 and the public welfare mandate to consider Client L's exposure, proactively contacting Client L is ethically permissible only if factually accurate and non-solicitative, and the safest course given Engineer A's competitive stake is to avoid independent notification of Client L entirely, leaving that channel to the regulatory process.

The Board resolved the tension between collegial engagement and mandatory reporting by distinguishing the present case from BER 96-8 on the ground that the prior case's extended deliberative tolerance was justified by a confidentiality obligation that does not exist here, thereby compressing the permissible window for collegial resolution and treating Engineer A's formal reporting duty as triggered promptly if Engineer X fails to respond or commits to immediate remediation.

The Board concluded that Engineer A bears an affirmative verification duty calibrated to reasonable professional confidence rather than absolute certainty, satisfied by a good-faith review of publicly available State P licensure records, because this threshold protects Engineer X from erroneous reports and protects Engineer A from the professional consequences of a false report, while not creating a procedural barrier that indefinitely delays action on a confirmed violation.

The Board concluded that Engineer A's competitive stake does not eliminate the reporting obligation but does impose a heightened duty of self-scrutiny at each procedural step, and that the graduated reporting sequence itself functions as a structural safeguard against weaponization of the regulatory process, because it requires Engineer A to demonstrate corrective intent before escalation rather than using the report as a first-strike competitive tool.

The Board concluded that the ethical framework is not static across all non-compliance scenarios: where non-compliance appears inadvertent, the collegial-first approach is not only appropriate but ethically required to give Engineer X a meaningful opportunity to cure; where non-compliance is willful, the collegial step either collapses into futility or has already been effectively completed, making the formal reporting obligation more immediate and less discretionary because the public welfare rationale for graduated response is undermined by demonstrated deliberate disregard.

The board concluded that Engineer A has no affirmative obligation to directly contact Client L because the former-client relationship does not sustain a fiduciary duty, the competitive context makes direct disclosure ethically suspect under III.7, and the licensure board reporting mechanism is the proper instrument for protecting Client L and the public - with direct contact reserved only for circumstances of imminent safety risk not present on these facts.

The board concluded that the Collegial Pre-Reporting Engagement principle and the Mandatory Reporting Obligation principle are not irreconcilable, but that Engineer A's competitive interest sharpens the risk of abuse - requiring that the collegial phase be treated as a bounded, good-faith opportunity for Engineer X to cure the violation, after which the reporting obligation activates unconditionally if no satisfactory resolution is achieved.

The board concluded that from a deontological perspective Engineer A does not have an unconditional duty to report immediately, but does have a categorical duty to verify promptly and in good faith - because the Kantian framework simultaneously grounds the reporting duty in universalizability and the verification duty in fairness to Engineer X as a rational agent - and that once verification and collegial engagement are complete without resolution, the duty to report is categorical and unaffected by Engineer A's competitive motivation.

The board concluded that the collegial-first approach does reflect the disposition of a professionally virtuous engineer when applied in good faith, but that Engineer A's competitive context creates a genuine risk that the collegial contact becomes a performance masquerading as professional courtesy - and that virtue ethics requires Engineer A to engage in honest self-examination about whether the motivational structure behind the contact is one of professional solidarity or competitive instrumentalization.

The board concluded that the graduated reporting sequence produces better consequentialist outcomes than immediate mandatory reporting because it filters out the likely majority of inadvertent, promptly remedied violations while preserving formal reporting for cases that genuinely require regulatory intervention - serving public welfare, licensure system integrity, and professional trust simultaneously - with the risk of ongoing unlicensed practice during the collegial phase mitigated by the time-bounded nature of that phase and the lower immediacy of safety risk characteristic of certificate of authority violations.

The board concluded that competitive motivation does not alter the reporting sequence but does introduce two additional obligations - motivational transparency and a higher verification threshold - because the competitive context transforms an innocent oversight into potential Code III.7 exposure, making each step in the graduated framework carry greater ethical weight for Engineer A than it would for a disinterested reporter.

The board concluded that Engineer A's obligation to report to the State P licensure board became substantially immediate upon Engineer X's acknowledgment and continued practice, because the collegial engagement had run its full course - the graduated framework's precondition was satisfied, the inadvertence rationale was eliminated, and the pending-application claim, while mitigating, did not confer lawful authority to continue practice.

The board concluded that Engineer A would face significant ethical exposure under Code III.7 because the competitive context transforms the failure to consult publicly available licensure records from an innocent oversight into conduct that at minimum raises the inference of reckless disregard for Engineer X's reputation, illustrating that the verification obligation is the mechanism by which a competitor-reporter demonstrates public-interest rather than self-interested motivation.

The board concluded that the apparent conflict between collegial engagement and mandatory reporting is resolved through structured sequencing rather than subordination: collegial contact is a procedural precondition that shapes when and how the reporting duty is discharged, but it cannot extinguish that duty, and once collegial engagement fails, the mandatory reporting obligation reasserts itself with full force and is not further defeatable by appeals to professional courtesy.

The board concluded that Engineer A's competitive motivation and the epistemic verification obligation are not in conflict but are structurally aligned - the presence of competitive interest is precisely the reason the verification threshold must be higher, not lower, because the risk of a biased certainty assessment is greatest when the reporter stands to benefit from the outcome, and Code III.7 makes the consequences of acting on unverified information against a competitor a substantive professional misconduct issue.

The Board concluded that mixed-motive reporting is ethically permissible when the underlying duty is genuine, the procedural sequence (verification, collegial contact, formal report) is followed, and the epistemic standard is met, because the ethical validity of the reporting obligation derives from conformity with Code-prescribed conduct rather than from the purity of Engineer A's motivation - but the Board simultaneously imposed a continuing self-scrutiny obligation on Engineer A to ensure that competitive interest does not distort the timing, framing, or escalation of the report, thereby preserving the integrity of the process even when the actor's motivations are irreducibly mixed.

Must Engineer A independently verify XYZ Engineering's certificate of authority status through authoritative sources before taking any formal or informal action, and what level of epistemic certainty is required before treating the matter as a confirmed violation?

Should Engineer A first contact Engineer X directly to counsel him about the certificate of authority deficiency and afford an opportunity to remedy it, or should Engineer A proceed immediately to file a report with the State P licensing board?

When contacting Engineer X, should Engineer A provide a full explanation of the certificate of authority requirement's purposes and legal consequences of non-compliance, or limit the communication to a bare notification of the apparent violation?

If Engineer X fails to remedy the certificate of authority deficiency after collegial contact, is Engineer A obligated to report XYZ Engineering's unauthorized practice to the State P licensing board, and how should Engineer A ensure the report is professionally rather than competitively motivated?

How should Engineer A structure his internal deliberation and external conduct to ensure that competitive self-interest does not corrupt his professional motivation at any stage of the response to XYZ Engineering's certificate of authority deficiency?