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.

Cited as an instructive example of how to balance the duty to report violations of safety codes with collegiality, establishing that the engineer should first seek clarification and early resolution with the offending engineer before reporting to authorities.

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.

The Board's recommendation implicitly separates the factual question (does XYZ Engineering lack a certificate of authority) from the motivational question (why is Engineer A raising it). Even though Engineer A is a business competitor of Engineer X and Client L is a former client of Engineer A's firm, these facts do not disqualify Engineer A from acting on legitimate knowledge of a licensure deficiency. The Code's reporting obligation under II.1.f is triggered by knowledge of a violation, not by the purity of the reporter's motives. However, the collegial consultation step serves the additional function of testing whether Engineer A's concern is well-founded before any reputational harm occurs, which indirectly guards against the appearance of using licensure enforcement as a competitive weapon.

The Board's conclusion establishes a two-stage process (collegial clarification, then possible reporting) but does not specify a time limit for the first stage. This creates an implicit obligation for Engineer A to pursue clarification promptly and diligently, since undue delay could itself frustrate the public protection purpose of III.8.a and II.1.f. Engineer A must balance affording Engineer X a genuine opportunity to explain or correct the deficiency against the risk that a lingering unauthorized practice situation continues to expose Client L to contract enforcement problems in State P during the interim.

The Board's recommendation does not resolve whether a prompt, voluntary correction by Engineer X (e.g., immediately obtaining the certificate of authority) would fully discharge Engineer A's reporting obligation. A reasonable extension of the Board's reasoning is that the purpose of II.1.f is prospective protection of the public and the integrity of the licensure system in State P, not punishment for a technical lapse that has been cured. If Engineer X's explanation shows the omission was inadvertent and has been remedied before Engineer A's inquiry or shortly thereafter, Engineer A may reasonably conclude that reporting is unnecessary, since the underlying risk to Client L and the public has been eliminated. Engineer A retains discretion to report if the explanation is unsatisfactory or if correction is not verified.

Regarding Q101, the fact that Engineer A is both a business competitor of Engineer X and previously served Client L does not by itself compromise the ethical propriety of raising the licensure issue. The Code's reporting obligation under II.1.f is triggered by knowledge of an apparent violation, not by the reporter's business relationships; however, this dual interest reinforces why the Board recommends a collegial, fact-clarifying first step rather than an immediate report, since this approach guards against the appearance that Engineer A is using licensure concerns to disadvantage a competitor or reclaim a former client.

Regarding Q102, Engineer A's ethical duties under the Code run primarily to the profession and the licensure board rather than directly to Client L. Nothing in II.1.f, III.7, or III.8.a creates an affirmative duty for Engineer A to warn Client L about XYZ Engineering's missing certificate of authority. Any benefit to Client L from resolution of the licensure issue is incidental to Engineer A's obligations of collegial consultation and, if warranted, reporting to the state board.

Regarding Q104, if Engineer X's clarification shows the lapse was inadvertent and has since been corrected, Engineer A's collegial consultation duty would be considered fulfilled, and the obligation to report to the licensure board would not necessarily be activated. The Code's reporting requirement is meant to address ongoing or unremedied violations that threaten public protection, not isolated administrative lapses that have already been cured.

Regarding Q301, from a deontological standpoint the Code does not mandate immediate reporting under II.1.f before any clarification is sought. Engineer A's duty of collegial consultation functions as a preliminary, rule-consistent step: engineers are expected to verify the factual basis of an alleged violation before formally invoking the reporting duty, since erroneous or premature reporting could itself violate the prohibition on injuring a colleague's reputation under III.7.

Regarding Q302, from a consequentialist perspective, Engineer A's approach of first privately consulting Engineer X is likely to produce the best overall outcome for licensure integrity and public protection in State P. If the certificate issue is quickly remedied through informal contact, the public and Client L are protected without the reputational and procedural costs of a premature formal complaint; if the issue is not resolved, escalation to the state board remains available and appropriate.

Regarding Q401, even absent any former client relationship between Engineer A and Client L, the Board's reasoning would likely still favor a collegial approach to Engineer X before reporting. The obligation not to maliciously or falsely injure a fellow engineer's reputation under III.7 applies independent of any competitive or client-based motive, meaning Engineer A's duty to seek clarification first would remain unchanged.

Regarding Q402, if XYZ Engineering had possessed a valid certificate of authority in State P, no ethical obligation would have arisen for Engineer A to contact Engineer X or to report to the licensure board, since the underlying premise triggering both the collegial consultation duty and the potential reporting duty is the apparent registration violation under III.8.a.

The Board resolved the apparent tension between Collegial Counseling of Engineer X and Licensure Compliance in State P not by ranking one principle above the other, but by sequencing them: collegial clarification functions as a mandatory first procedural step, while formal reporting under the Licensure Violation Reporting Duty remains the fallback obligation if that clarification fails. This shows that collegiality and compliance enforcement are not competing values but successive stages of a single ethical process—informal peer engagement is a precondition for, not a substitute for, eventual enforcement action.

The risk that Engineer A's Independent Judgment in Business Practice could be tainted by competitive self-interest toward a former client is managed procedurally rather than resolved substantively: by requiring direct engagement with Engineer X before any conclusion or report, the Code channels potentially self-interested suspicion into a verifiable, fact-based process. This suggests that Certificate of Authority Compliance is applied impartially only insofar as the reporting engineer first submits the allegation to a check (the accused's explanation) that neutralizes personal motive before formal action is taken.

Certificate of Authority Compliance operates in this case as a strict, non-negotiable rule (a licensure fact either exists or does not), whereas Collegial Counseling of Engineer X is a relationship-based, discretionary norm governing how that fact is investigated. The case demonstrates that flexible collegial norms can govern the *manner* of enforcing a strict rule without diluting the rule's substantive force—Engineer A's ultimate duty to report, if warranted, is preserved intact even while courtesy governs the initial approach.

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

Does Engineer A's status as a competitor and the fact that Client L is a former client raise a question about whether Engineer A's motives in pursuing this matter are purely ethical or partly self-interested?

Does Engineer A have any obligation to inform Client L directly that XYZ Engineering may lack a certificate of authority in State P, given the potential exposure to contract enforcement problems for Client L's project?

How should Engineer A determine how much time to allow for collegial clarification before escalating to a formal report, given that unreasonable delay could itself constitute a lapse in Engineer A's reporting duty?

If Engineer X's explanation reveals that the missing certificate of authority was inadvertent and quickly remedied, does Engineer A still bear an obligation to report the matter to the licensure board, or does the collegial resolution satisfy the ethical requirement?

How should Engineer A balance the duty of Collegial Counseling of Engineer X against the Licensure Compliance in State P principle, which may require prompt formal reporting rather than informal peer clarification?

Does Engineer A's Independent Judgment in Business Practice, which could be shaped by competitive interest in a former client, conflict with the impartial application of Certificate of Authority Compliance standards to Engineer X?

How should Engineer A reconcile the obligation of Collegial Counseling of Engineer X with the risk that raising the licensure issue directly could be perceived as an attempt to injure a competitor's professional reputation, contrary to III.7?

Is there a tension between Certificate of Authority Compliance as a strict licensure rule and the more flexible, relationship-based approach embodied in Collegial Counseling of Engineer X, and how should Engineer A weigh strict rule enforcement against professional courtesy?

From a deontological perspective, did Engineer A fulfill the duty to seek clarification (collegial consultation) before invoking the reporting obligation under II.1.f, or does the Code require immediate reporting once knowledge of a possible violation is acquired?

Did the likely outcome of preserving licensure integrity and public protection in State P justify Engineer A's approach of first privately consulting Engineer X rather than immediately reporting the apparent certificate deficiency to the state board?

Did Engineer A act with professional integrity and collegiality by choosing to engage Engineer X directly for clarification rather than assuming misconduct and reporting a business competitor outright?

If Client L had never been a former client of Engineer A's firm, would the Board still have found that Engineer A had a proper basis to approach Engineer X collegially, given that Engineer A is Engineer X's competitor and III.7 prohibits maliciously injuring a fellow engineer's reputation?

If XYZ Engineering had in fact possessed a valid certificate of authority to practice in State P, would Engineer A have had any obligation at all to contact Engineer X or to report the matter to the state licensure board?

Engineer Retention, though carrying no direct normative fulfillment or violation itself, sets the causal chain in motion that later exposes Engineer X's certificate omission, showing that even normatively neutral acts can trigger significant downstream compliance issues.

Certificate Omission violates the Compliance with State Engineering Licensure Laws obligation, and this violation is precisely what causes the Certificate Deficiency Discovery, making the omission the root normative failure that necessitates all subsequent corrective actions.

Collegial Counseling Discussion fulfills the obligation to engage collegially and cooperatively, and because it is guided by collegiality, avoiding premature judgment, and independent discretion, it responsibly channels the discovered certificate deficiency toward remediation via Certificate Acquisition rather than immediate punitive escalation.

Certificate Acquisition fulfills the Compliance with State Engineering Licensure Laws obligation, directly remedying the earlier violation caused by Certificate Omission and demonstrating that the collegial discussion successfully resolved the licensure deficiency rather than allowing it to persist.

The question arises because Engineer A, as a competitor and former colleague of Engineer X, possesses knowledge of a licensure deficiency that could be addressed either through formal reporting or informal peer correction, and the facts do not specify which path professional ethics obligates him to take first.

The question arises because Engineer A's dual identity as competitor and former service provider to Client L makes his otherwise legitimate licensure concern ambiguous in motive, since the same data supports both an ethical and a self-interested reading.

The question arises because Engineer A possesses information that could materially affect Client L's legal position, yet professional norms of collegiality and caution against premature conclusions create tension over whether disclosure obligations run to the client or should first be mediated through the peer engineer.

The question arises because Toulmin's model shows two valid obligations, collegial engagement and timely reporting, both authorized by the same triggering fact, with no bright-line rule specifying when one warrant's authority yields to the other.

The question arose because Engineer A's collegial engagement with Engineer X produced a satisfactory factual explanation and correction, creating tension between the rule-based duty to report licensure violations and the practice-based value of resolving matters collegially before escalating to formal channels.

The question arises because the same fact pattern, an unlicensed firm practicing in State P, supports two legitimate but conflicting professional obligations, collegial peer counseling and formal regulatory reporting, and the case does not specify which threshold of certainty or urgency should trigger escalation from one to the other.

The question arises because the same set of facts, a former client relationship and a discovered licensure deficiency, can be interpreted either as legitimate professional concern or as self-interested competitive behavior, and Toulmin's model shows this ambiguity stems from unresolved rebuttal conditions about Engineer A's actual motives and ongoing interests.

The question arises because the same fact, Engineer A's knowledge of XYZ's licensure gap, supports both a collegial duty to inform a peer and a competing prohibition against actions that could be construed as harming a competitor's standing, leaving the correct course of action contested.

The question arose because Engineer A possesses both a formal enforcement obligation and a collegial relationship with Engineer X, and the facts do not clarify which obligation should take precedence given the ambiguous severity and intent behind the certificate omission.

The question arose because Engineer A faced a deficiency that could be either an innocent oversight or a genuine violation, and the Code's language leaves ambiguous whether collegial consultation is a prerequisite to, or can be bypassed by, the reporting obligation under II.1.f.

The question arises because Engineer A's knowledge of a possible licensure gap creates two plausible, competing obligations, immediate public protection through reporting versus professional courtesy through direct peer consultation, and it is unclear which better served the public interest given the ambiguity about whether the omission was inadvertent.

The question arises because Engineer A possesses knowledge of a potential licensure deficiency by a business competitor, creating tension between a duty to protect the public through reporting and a duty to avoid premature conclusions and act collegially toward a peer.

The question arises because the Board's finding of propriety rests on a specific factual anchor, the former client relationship, and removing that anchor exposes a latent tension between the duty of collegial engagement and the III.7 prohibition on maliciously injuring a competitor's reputation.

The question arises because it isolates whether Engineer A's obligation depends strictly on the factual existence of a licensure violation or on some independent duty of vigilance, making the counterfactual necessary to test the warrant's scope.

Given that Engineer A only suspects, rather than confirms, that XYZ Engineering lacks a certificate of authority, the Board concluded that collegial clarification should precede any formal report, reserving escalation for cases where Engineer X's explanation proves unsatisfactory.

Given that Engineer A's competitive relationship with Engineer X and prior relationship with Client L do not by themselves negate legitimate knowledge of a deficiency, the Board concluded that motive does not disqualify the reporting trigger, but recommended collegial consultation as a safeguard against the appearance of using licensure rules competitively.

Because the Board's two-stage process leaves the clarification period undefined, it follows that Engineer A must act with reasonable promptness so that the collegial step does not itself become a vehicle for prolonging the public's exposure to an unauthorized practice situation.

Assuming Engineer X's lapse was inadvertent and promptly cured, the Board's rationale supports treating the collegial resolution as sufficient, since the risk to Client L and the public has been eliminated, but Engineer A retains discretion to report if the cure is unverified.

Given that Engineer A's business relationships do not themselves undermine the legitimacy of the licensure concern, the Board concluded that the reporting trigger remains intact, while recommending collegial clarification as a means of dispelling any appearance of self-interested motive.

Because Client L was only a former client and the Code's provisions on reporting and registration compliance are framed toward the profession and licensure board, the board concluded Engineer A owed no direct warning duty to Client L, with any client benefit being incidental to the collegial and reporting obligations owed to the profession.

Given that Engineer X's clarification revealed an inadvertent and already-corrected certificate lapse, the board concluded that Engineer A's collegial consultation duty was satisfied and that formal reporting was not required, since the Code's reporting mechanism targets unremedied threats to public protection rather than cured administrative errors.

Because the certificate deficiency was not yet confirmed as a genuine, unremedied violation, the board concluded that seeking clarification from Engineer X first was consistent with, not contrary to, the deontological duty in II.1.f, since premature reporting risked violating III.7's prohibition on injuring a colleague's reputation.

Given that formal escalation remained available as a fallback, the board concluded that Engineer A's choice to first consult Engineer X privately was the consequentially superior approach, since it protected licensure integrity and the public while avoiding unnecessary reputational harm if the issue proved to be a quickly curable lapse.

Even supposing Client L had never been Engineer A's client, the board concluded that the collegial consultation duty toward Engineer X would still apply, since III.7's prohibition on maliciously or falsely injuring a fellow engineer's reputation operates independently of any competitive or client-based motive Engineer A might have had.

Given that the entire chain of obligations rests on an apparent violation of III.8.a, the board concluded that if that predicate fact were absent, Engineer A would have no occasion to invoke either the collegial consultation duty or the reporting duty, because both are downstream of the same triggering condition.

Given that a collegial path to Engineer X was open and the underlying fact was only an apparent violation pending explanation, the board reasoned that clarification functions as a mandatory precondition to reporting rather than a competing alternative to it, so the two obligations operate in sequence rather than in tension.

Given that Client L's status as a former client and Engineer A's position as a competitor created a plausible motive for bias, the board concluded that requiring direct engagement with Engineer X before any action functions as a procedural safeguard that channels potentially self-interested suspicion into a fact-checked process rather than resolving the bias question directly.

Given that Certificate of Authority Compliance depends on an objective fact while Collegial Counseling concerns interpersonal manner, the board concluded that the two operate at different levels, so Engineer A can extend courtesy to Engineer X during investigation without weakening the eventual duty to report if the fact of noncompliance is confirmed.

Should Engineer A first seek collegial clarification from Engineer X before considering a formal report, or report the suspected violation immediately to the licensure board?

If Engineer X's explanation shows the certificate omission was inadvertent and promptly corrected, should Engineer A still report the matter to the licensure board?

Does Engineer A's status as a competitor of Engineer X and prior relationship with Client L disqualify Engineer A from raising the licensure concern, or may Engineer A act on the factual knowledge regardless of these relationships?

Should Engineer A directly inform Client L that XYZ Engineering may lack a certificate of authority in State P?