Step 4: Full View
Entities, provisions, decisions, and narrative
Full Entity Graph
Loading...Entity Types
Synthesis Reasoning Flow
Shows how NSPE provisions inform questions and conclusions - the board's reasoning chainNode Types & Relationships
→ Question answered by Conclusion
→ Provision applies to Entity
NSPE Code Provisions Referenced
View ExtractionI.4. I.4.
Full Text:
Act for each employer or client as faithful agents or trustees.
Applies To:
II.3.a. II.3.a.
Full Text:
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.
Applies To:
II.5. II.5.
Full Text:
Engineers shall avoid deceptive acts.
Applies To:
II.5.a. II.5.a.
Full Text:
Engineers shall not falsify their qualifications or permit misrepresentation of their or their associates' qualifications. They shall not misrepresent or exaggerate their responsibility in or for the subject matter of prior assignments. Brochures or other presentations incident to the solicitation of employment shall not misrepresent pertinent facts concerning employers, employees, associates, joint venturers, or past accomplishments.
Applies To:
III.1. III.1.
Full Text:
Engineers shall be guided in all their relations by the highest standards of honesty and integrity.
Applies To:
III.3.a. III.3.a.
Full Text:
Engineers shall avoid the use of statements containing a material misrepresentation of fact or omitting a material fact.
Applies To:
III.6. III.6.
Full Text:
Engineers shall not attempt to obtain employment or advancement or professional engagements by untruthfully criticizing other engineers, or by other improper or questionable methods.
Applies To:
I.1. I.1.
Full Text:
Hold paramount the safety, health, and welfare of the public.
Applies To:
Cited Precedent Cases
View ExtractionBER Case 97-11 distinguishing linked
Principle Established:
An engineer is not automatically compelled to disclose a pending ethics complaint to a client, as a complaint is a mere allegation and not a finding of fact; however, the engineer should weigh providing limited background information to the client in a dispassionate manner.
Citation Context:
The Board cited this case to establish the baseline obligation of disclosure to clients regarding pending ethics complaints, then distinguished it from the present case because Engineer F's contractor license revocation was an actual adjudication of wrongdoing rather than a mere allegation.
Relevant Excerpts:
"The first is BER Case 97-11 , where Engineer A was retained by Client B to perform design services and provide a Critical Path Method (CPM) schedule for a manufacturing facility."
"Clearly, a major difference between BER Case 97-11 and the present case is that here, Engineer F had his contractor's license revoked because of actual demonstrated violation on Engineer F's part."
BER Case 75-5 supporting linked
Principle Established:
Personal misconduct not directly related to the practice of engineering is still subject to the NSPE Code of Ethics, because the purpose of a code of ethics is to ensure the public can have confidence in the integrity, honesty, and decorous behavior of professional practitioners.
Citation Context:
The Board cited this case to support the principle that personal misconduct unrelated to the direct practice of engineering can still constitute a violation of the NSPE Code of Ethics, broadening the ethical analysis beyond Engineer F's engineering license to his contractor license revocation.
Relevant Excerpts:
"The second case that relates to the instant case is BER Case 75-5 , where the BER found that personal misconduct that was not related to the practice of engineering was a violation of the NSPE Code of Ethics."
"BER Case 75-5 clearly indicates that the BER must look beyond just the specific practice of engineering to the whole person when addressing ethical issues relating to professional engineers."
Questions & Conclusions
View ExtractionQuestion 1 Board Question
Did Engineer F have an ethical obligation to report on the employment application the revocation of his contractor’s license?
Engineer F had an ethical obligation to report on the employment application the revocation of his contractor’s license.
Question 2 Implicit
Does the ethical obligation to disclose the contractor license revocation change depending on whether the employment application question was drafted narrowly by the hiring firm, and does the firm's imprecise drafting bear any moral weight in distributing responsibility for the omission?
The narrow wording of the employment application question does not meaningfully redistribute moral responsibility for Engineer F's omission to the hiring firm. While the engineering firm could have drafted a more comprehensive disciplinary inquiry question, the ethical obligation to disclose material integrity information flows from Engineer F's own duties under the NSPE Code - not from the precision of the questioner's drafting. An engineer who exploits an imprecisely worded question to omit an adjudicated integrity violation is not acting as a faithful agent or trustee; he is engaging in legalistic self-protection that the Code explicitly prohibits. The firm's imperfect drafting may reflect a due diligence gap on its part, but it does not constitute a moral license for Engineer F to withhold information that any reasonable employer would consider material to a hiring decision. The ethical obligation to avoid deceptive acts and technically misleading statements is self-executing - it does not depend on the sophistication of the question posed.
The Allegation-Adjudication Distinction - used to differentiate Engineer F's case from BER Case 97-11, where Engineer A faced only a pending ethics complaint - resolves a latent tension between the Prudential Disclosure principle and the Omission Materiality principle by establishing a graduated disclosure threshold rather than a binary rule. Under BER 97-11, the Board declined to impose a categorical obligation on Engineer A to disclose a mere allegation, recognizing that unresolved complaints carry uncertain probative weight and that premature disclosure could itself be misleading or unfair. In Engineer F's case, however, the contractor license revocation is an adjudicated finding: a formal governmental determination that Engineer F committed a specific integrity violation. The synthesis of these two cases teaches that the disclosure obligation is calibrated to epistemic certainty and adjudicative finality: allegations occupy a zone of prudential weighing where disclosure may be advisable but is not categorically required, while adjudicated findings of wrongdoing - particularly those involving integrity violations in safety-sensitive domains - cross a threshold of materiality that makes non-disclosure on a professional employment application an ethics violation. The principle hierarchy is therefore: Omission Materiality (adjudicated findings) > Prudential Disclosure (allegations), with the Allegation-Adjudication Distinction serving as the operative boundary between the two regimes. This also implies that the moral responsibility for the informational gap created by the firm's narrow application drafting diminishes as the certainty and severity of the undisclosed finding increases - Engineer F cannot shift responsibility to the firm's imprecise drafting when the omitted fact is an adjudicated revocation for an integrity violation.
Question 3 Implicit
Beyond the initial employment application, did Engineer F acquire a continuing or renewed ethical obligation to disclose the contractor license revocation to his employer once he was hired, and if so, at what point does that obligation arise?
The Board's reasoning, read in light of its comparative analysis distinguishing BER Case 97-11, establishes a meaningful threshold: an adjudicated finding of wrongdoing - as opposed to a pending allegation or unresolved complaint - triggers a firm disclosure obligation on a professional employment application even when the disciplinary action arose outside the PE license domain. This allegation-adjudication distinction is not merely procedural; it reflects the epistemic difference between an unproven claim and a formally determined fact about the applicant's character. Because Engineer F's contractor license revocation was a completed adjudication, he could not invoke the uncertainty or reputational-harm rationale that might counsel caution about disclosing unresolved allegations. Furthermore, the Board's reasoning implies a continuing obligation: once hired, Engineer F's duty as a faithful agent and trustee to his employer would independently require disclosure of the revocation, since concealing a material adjudicated integrity finding from an employer who would reasonably consider it relevant to the employment relationship is inconsistent with the faithful agency canon. The ethical obligation thus did not expire at the moment of hiring but persisted as a relational duty throughout the employment relationship.
Engineer F's ethical obligation to disclose the contractor license revocation did not terminate upon submission of the employment application. Once hired, Engineer F entered into a fiduciary-adjacent relationship with his employer as a faithful agent and trustee under the NSPE Code. That relationship independently activates a continuing duty of candor regarding material facts bearing on his fitness and integrity. The moment Engineer F became aware that his employer was operating under a materially incomplete understanding of his professional history - an understanding Engineer F himself had created through omission - a renewed and arguably stronger disclosure obligation arose. This obligation would crystallize at the latest when the employer's reliance on the incomplete record became consequential, such as when Engineer F was assigned to projects, given supervisory authority, or held out to clients as a qualified professional. Silence in the face of a known material omission, once an employment relationship has been established, compounds rather than cures the original ethical breach.
Question 4 Implicit
Would Engineer F's ethical disclosure obligation differ if the contractor license revocation had been for a purely administrative or technical violation unrelated to integrity - such as a paperwork lapse - rather than for allowing an unlicensed individual to misuse his license number?
Engineer F's disclosure obligation would be materially weaker if the contractor license revocation had arisen from a purely administrative or technical violation - such as a paperwork lapse or failure to renew on time - rather than from the integrity-implicating conduct of allowing an unlicensed individual unrelated to his firm to use his contractor license number. The ethical weight of a disclosure obligation scales with the character relevance of the underlying conduct. Administrative failures speak primarily to organizational competence; they do not necessarily implicate the honesty, trustworthiness, or professional integrity that the NSPE Code's whole-person character standard is designed to assess. By contrast, deliberately lending a license number to an unrelated unlicensed individual is an affirmative act of deception that undermines the very licensing system designed to protect the public - conduct that sits at the core of what the Code's integrity provisions address. The adjudicated nature of the revocation matters, but so does the moral character of the underlying act. A purely technical revocation might fall below the materiality threshold for mandatory disclosure on a PE employment application; the actual conduct here clearly does not.
Question 5 Implicit
Does the fact that Engineer F's misconduct - lending his contractor license number to an unrelated unlicensed individual - directly implicates the same professional integrity norms that govern PE licensure create a heightened disclosure obligation compared to a contractor license revocation arising from entirely unrelated conduct?
The Board's conclusion that Engineer F had an ethical obligation to disclose the contractor license revocation rests not merely on the fact of revocation but on the nature of the underlying conduct: deliberately allowing an unlicensed individual unrelated to his firm to use his contractor license number. This act directly implicates the same professional integrity norms - honesty, faithful agency, and protection of the public - that govern PE licensure. Because the misconduct was not a technical or administrative lapse but an affirmative integrity violation adjudicated through a formal proceeding, the ethical obligation to disclose was heightened beyond what would apply to a purely procedural license deficiency. The safety-critical domain of fire sprinkler contracting further amplifies this materiality, since the public safety stakes of that field mirror those that animate engineering ethics codes generally. Accordingly, Engineer F's disclosure obligation was not merely triggered by the existence of a revocation but was intensified by the character of the conduct that produced it.
The fact that Engineer F's misconduct - lending his contractor license number to an unrelated unlicensed individual - directly implicates the same professional integrity norms that govern PE licensure creates a heightened, not merely equivalent, disclosure obligation. Licensing systems across engineering and contracting domains share a common foundational purpose: ensuring that only qualified, accountable individuals perform work that affects public safety. When an engineer subverts that system in one licensed domain by enabling unlicensed practice, the conduct speaks directly to his fitness to be trusted with the responsibilities of PE licensure in another. The fire protection context amplifies this further: fire sprinkler systems are life-safety infrastructure, and allowing an unlicensed individual to operate under a contractor license number in that domain is not a technical irregularity but a public safety violation. The cross-domain integrity relevance and the safety-critical nature of the field together elevate the materiality of the revocation well beyond what would apply to a license revocation in an unrelated, non-safety-sensitive domain.
Question 6 Principle Tension
Does the principle that engineers are entitled to rely on the literal scope of a question asked of them - Employment Application Question Scope Fidelity - conflict with the principle that technically true but misleading answers are ethically prohibited, and how should an engineer resolve that tension when the question's wording is narrower than its evident purpose?
The Board's conclusion implicitly rejects the argument that Engineer F could ethically rely on the narrow literal wording of the employment application question - which referenced only discipline 'in the practice of professional engineering' - to justify omitting the contractor license revocation. Under the NSPE Code's prohibition on deceptive acts and its requirement that engineers avoid statements containing material omissions that create false impressions, a technically accurate answer that is crafted to exploit a question's imprecise drafting is ethically equivalent to a misrepresentation when the omitted information is material to the purpose the question was plainly designed to serve. The evident purpose of the disciplinary question was to assess the applicant's character and fitness for professional trust, not merely to audit PE license status in a narrow administrative sense. Engineer F's exploitation of the question's literal scope to conceal an adjudicated integrity violation therefore constitutes the kind of artfully misleading omission the Code prohibits, regardless of whether his PE license itself was ever disciplined. The firm's failure to draft a more comprehensive question does not transfer moral responsibility for the omission to the firm; the duty of candor rests with the applicant.
The tension between Employment Application Question Scope Fidelity - the notion that an engineer may answer only what is literally asked - and the prohibition on technically true but misleading statements is resolved decisively in favor of the latter under the NSPE Code. The Code does not permit an engineer to treat a questioner's imprecise drafting as a loophole through which material integrity information may be withheld. The evident purpose of the employment application's disciplinary question was to assess whether the applicant had a history of adjudicated professional misconduct bearing on his fitness for a PE role. Engineer F's answer was technically accurate in its narrowest reading but functionally deceptive in its effect: it conveyed to the hiring firm that no relevant disciplinary history existed, when in fact an adjudicated revocation for an integrity violation in a safety-critical licensed domain did exist. The Code's provisions on deceptive acts and material omissions are not satisfied by literal accuracy alone; they require that the overall impression conveyed be truthful. Engineer F's answer failed that standard.
The tension between Employment Application Question Scope Fidelity - the idea that an applicant may legitimately confine answers to the literal scope of a question - and the Technically True But Misleading Statement Prohibition was resolved decisively in favor of the latter. The Board implicitly held that when a question's evident purpose is to assess character and fitness for professional trust, an engineer cannot exploit narrow drafting to suppress a material adjudicated integrity violation. The narrow wording of the application question ('disciplined in the practice of professional engineering or had his license suspended or revoked') did not exculpate Engineer F because the ethics code imposes a duty to interpret such questions according to their evident purpose rather than their most self-serving literal reading. This resolution teaches that Question Scope Fidelity is a subordinate principle: it governs genuinely ambiguous or irrelevant omissions, but it yields entirely when the omitted information is both material to the questioner's evident purpose and reflects an adjudicated finding of wrongdoing by the applicant. The principle hierarchy is therefore: Technically True But Misleading Statement Prohibition > Employment Application Question Scope Fidelity, whenever the gap between literal scope and evident purpose is exploited to conceal integrity-relevant conduct.
Question 7 Principle Tension
How should the Whole-Person Character Integrity Standard - which extends ethical scrutiny to non-engineering conduct - be reconciled with the principle that the ethics code's jurisdiction is ordinarily bounded by professional engineering practice, given that Engineer F's contractor license revocation arose outside his PE role?
The Whole-Person Character Integrity Standard drawn from BER Case 75-5 can be reconciled with the ordinary jurisdictional boundaries of the engineering ethics code by recognizing that the Code's reach is not defined by the domain in which conduct occurs, but by whether the conduct is relevant to the engineer's fitness to fulfill professional engineering obligations. The Code does not claim jurisdiction over every aspect of an engineer's personal life; it does claim jurisdiction over conduct that bears on honesty, integrity, and public safety - wherever that conduct occurs. Engineer F's contractor license revocation arose outside his PE role but directly implicated the same integrity norms - prohibition on enabling unlicensed practice, protection of licensing system integrity, and public safety - that the PE ethics code enforces. The cross-domain character relevance, not the domain of occurrence, is the operative jurisdictional trigger. This reading avoids both over-extension of the Code into genuinely private conduct and under-extension that would allow engineers to compartmentalize integrity violations by domain.
The Whole-Person Character Integrity Standard - drawn from BER Case 75-5 and applied here to Engineer F's non-engineering contractor misconduct - was reconciled with the ordinarily bounded jurisdiction of the engineering ethics code by invoking the nature of the underlying conduct rather than the domain of the license. The Board's reasoning implicitly holds that the ethics code's jurisdiction extends beyond PE practice whenever the conduct in question directly implicates the same integrity norms - honesty, non-deception, faithful agency, and protection of public safety - that the code exists to enforce. Engineer F's act of lending his contractor license number to an unlicensed individual unrelated to his firm is not merely a regulatory infraction in a separate domain; it is a paradigmatic integrity violation that mirrors the very harms the engineering ethics code guards against: misrepresentation of qualifications, facilitation of unlicensed practice, and endangerment of public safety in a safety-critical field. The Domain-Relevance Amplification principle further reinforces this synthesis: because fire sprinkler contracting is directly safety-critical, the revocation carries heightened materiality that closes any residual gap between the contractor domain and the PE ethics domain. This case therefore teaches that the Whole-Person Character Integrity Standard activates - and overrides any domain-boundedness objection - when three conditions converge: (1) the non-PE conduct reflects an adjudicated integrity violation, (2) the violation mirrors core engineering ethics norms, and (3) the domain of the violation is safety-sensitive.
Question 8 Principle Tension
Does the Allegation-Adjudication Distinction - which the Board used to differentiate Engineer F's case from BER 97-11 - conflict with the Prudential Disclosure principle applied to Engineer A, and does that conflict suggest that adjudicated findings always trigger disclosure while mere allegations never do, or is there a more nuanced threshold?
The Board's reasoning, read in light of its comparative analysis distinguishing BER Case 97-11, establishes a meaningful threshold: an adjudicated finding of wrongdoing - as opposed to a pending allegation or unresolved complaint - triggers a firm disclosure obligation on a professional employment application even when the disciplinary action arose outside the PE license domain. This allegation-adjudication distinction is not merely procedural; it reflects the epistemic difference between an unproven claim and a formally determined fact about the applicant's character. Because Engineer F's contractor license revocation was a completed adjudication, he could not invoke the uncertainty or reputational-harm rationale that might counsel caution about disclosing unresolved allegations. Furthermore, the Board's reasoning implies a continuing obligation: once hired, Engineer F's duty as a faithful agent and trustee to his employer would independently require disclosure of the revocation, since concealing a material adjudicated integrity finding from an employer who would reasonably consider it relevant to the employment relationship is inconsistent with the faithful agency canon. The ethical obligation thus did not expire at the moment of hiring but persisted as a relational duty throughout the employment relationship.
The Allegation-Adjudication Distinction drawn by the Board to differentiate Engineer F's case from BER Case 97-11 does not establish a binary rule that allegations never trigger disclosure while adjudications always do. Rather, it identifies adjudication as a sufficient condition for disclosure - a threshold that, once crossed, removes the prudential weighing that Engineer A in BER 97-11 was permitted to perform. Engineer A faced an unresolved allegation whose truth was contested and whose disclosure could itself cause harm; the Board recognized that a pending complaint does not carry the same evidentiary weight as a completed proceeding. Engineer F faced a formally adjudicated revocation - a finding of fact by a competent authority that the misconduct occurred. The distinction is not categorical but evidentiary: adjudication eliminates the uncertainty that justified Engineer A's more cautious approach and replaces it with a settled factual record that the engineer cannot in good faith treat as ambiguous or unresolved. Between the poles of mere allegation and formal adjudication lies a spectrum of intermediate findings - consent orders, informal settlements, deferred revocations - each of which would require its own materiality analysis.
The tension between Employment Application Question Scope Fidelity - the idea that an applicant may legitimately confine answers to the literal scope of a question - and the Technically True But Misleading Statement Prohibition was resolved decisively in favor of the latter. The Board implicitly held that when a question's evident purpose is to assess character and fitness for professional trust, an engineer cannot exploit narrow drafting to suppress a material adjudicated integrity violation. The narrow wording of the application question ('disciplined in the practice of professional engineering or had his license suspended or revoked') did not exculpate Engineer F because the ethics code imposes a duty to interpret such questions according to their evident purpose rather than their most self-serving literal reading. This resolution teaches that Question Scope Fidelity is a subordinate principle: it governs genuinely ambiguous or irrelevant omissions, but it yields entirely when the omitted information is both material to the questioner's evident purpose and reflects an adjudicated finding of wrongdoing by the applicant. The principle hierarchy is therefore: Technically True But Misleading Statement Prohibition > Employment Application Question Scope Fidelity, whenever the gap between literal scope and evident purpose is exploited to conceal integrity-relevant conduct.
The Allegation-Adjudication Distinction - used to differentiate Engineer F's case from BER Case 97-11, where Engineer A faced only a pending ethics complaint - resolves a latent tension between the Prudential Disclosure principle and the Omission Materiality principle by establishing a graduated disclosure threshold rather than a binary rule. Under BER 97-11, the Board declined to impose a categorical obligation on Engineer A to disclose a mere allegation, recognizing that unresolved complaints carry uncertain probative weight and that premature disclosure could itself be misleading or unfair. In Engineer F's case, however, the contractor license revocation is an adjudicated finding: a formal governmental determination that Engineer F committed a specific integrity violation. The synthesis of these two cases teaches that the disclosure obligation is calibrated to epistemic certainty and adjudicative finality: allegations occupy a zone of prudential weighing where disclosure may be advisable but is not categorically required, while adjudicated findings of wrongdoing - particularly those involving integrity violations in safety-sensitive domains - cross a threshold of materiality that makes non-disclosure on a professional employment application an ethics violation. The principle hierarchy is therefore: Omission Materiality (adjudicated findings) > Prudential Disclosure (allegations), with the Allegation-Adjudication Distinction serving as the operative boundary between the two regimes. This also implies that the moral responsibility for the informational gap created by the firm's narrow application drafting diminishes as the certainty and severity of the undisclosed finding increases - Engineer F cannot shift responsibility to the firm's imprecise drafting when the omitted fact is an adjudicated revocation for an integrity violation.
Question 9 Principle Tension
Does the Domain-Relevance Amplification principle - which heightens disclosure obligations when the prior misconduct occurred in a safety-sensitive field like fire protection - conflict with the Omission Materiality principle's domain-neutral standard, and should disclosure obligations be calibrated to the safety stakes of the prior domain or applied uniformly regardless of subject matter?
The fact that Engineer F's misconduct - lending his contractor license number to an unrelated unlicensed individual - directly implicates the same professional integrity norms that govern PE licensure creates a heightened, not merely equivalent, disclosure obligation. Licensing systems across engineering and contracting domains share a common foundational purpose: ensuring that only qualified, accountable individuals perform work that affects public safety. When an engineer subverts that system in one licensed domain by enabling unlicensed practice, the conduct speaks directly to his fitness to be trusted with the responsibilities of PE licensure in another. The fire protection context amplifies this further: fire sprinkler systems are life-safety infrastructure, and allowing an unlicensed individual to operate under a contractor license number in that domain is not a technical irregularity but a public safety violation. The cross-domain integrity relevance and the safety-critical nature of the field together elevate the materiality of the revocation well beyond what would apply to a license revocation in an unrelated, non-safety-sensitive domain.
The Whole-Person Character Integrity Standard - drawn from BER Case 75-5 and applied here to Engineer F's non-engineering contractor misconduct - was reconciled with the ordinarily bounded jurisdiction of the engineering ethics code by invoking the nature of the underlying conduct rather than the domain of the license. The Board's reasoning implicitly holds that the ethics code's jurisdiction extends beyond PE practice whenever the conduct in question directly implicates the same integrity norms - honesty, non-deception, faithful agency, and protection of public safety - that the code exists to enforce. Engineer F's act of lending his contractor license number to an unlicensed individual unrelated to his firm is not merely a regulatory infraction in a separate domain; it is a paradigmatic integrity violation that mirrors the very harms the engineering ethics code guards against: misrepresentation of qualifications, facilitation of unlicensed practice, and endangerment of public safety in a safety-critical field. The Domain-Relevance Amplification principle further reinforces this synthesis: because fire sprinkler contracting is directly safety-critical, the revocation carries heightened materiality that closes any residual gap between the contractor domain and the PE ethics domain. This case therefore teaches that the Whole-Person Character Integrity Standard activates - and overrides any domain-boundedness objection - when three conditions converge: (1) the non-PE conduct reflects an adjudicated integrity violation, (2) the violation mirrors core engineering ethics norms, and (3) the domain of the violation is safety-sensitive.
From a deontological perspective, did Engineer F fulfill his categorical duty of honesty by answering 'no' to the employment application's disciplinary question, given that the question's literal wording referenced only professional engineering license discipline while his contractor's license had been formally revoked for a clear integrity violation?
From a deontological perspective, Engineer F did not fulfill his categorical duty of honesty by answering 'no' to the employment application's disciplinary question. Kantian ethics requires not merely that statements be literally true but that they be offered in a spirit consistent with the rational agency of the recipient - that is, that they not be designed to produce a false belief in the listener's mind. Engineer F's answer, while technically accurate as to PE license discipline, was crafted to exploit the question's narrow wording in a way that would predictably cause the hiring firm to believe no relevant disciplinary history existed. This is precisely the kind of deception by omission that deontological ethics condemns as a violation of the duty of truthfulness. The categorical imperative further condemns the underlying maxim: if all engineers were permitted to answer disciplinary questions by reference only to the narrowest possible reading of the question's literal scope, the entire institution of employment application disclosure would be rendered meaningless. Engineer F's conduct fails both the universalizability test and the duty of non-deception.
From a virtue ethics standpoint, does Engineer F's deliberate reliance on the narrow wording of the employment application question to omit a material adjudicated integrity violation reflect the character of a professional who embodies honesty and integrity as stable virtues, or does it reveal a disposition toward legalistic self-protection incompatible with the whole-person integrity standard expected of licensed engineers?
From a virtue ethics standpoint, Engineer F's deliberate reliance on the narrow wording of the employment application question to omit an adjudicated integrity violation reveals a disposition toward legalistic self-protection that is fundamentally incompatible with the whole-person integrity standard expected of licensed professional engineers. A person of genuine honesty and integrity does not scan a question for its narrowest defensible reading in order to withhold information the questioner would plainly want to know. That behavior reflects not the stable virtue of honesty but its simulacrum - a performance of technical compliance designed to achieve the benefits of candor's reputation without its substance. The virtue ethics framework asks what a person of good character would do; a person of good character in Engineer F's position would have recognized that the hiring firm's evident purpose was to assess fitness and integrity, and would have disclosed the revocation voluntarily, perhaps with context, rather than exploiting a drafting gap. Engineer F's conduct is not merely a rule violation; it is a character revelation.
From a consequentialist perspective, did Engineer F's omission of the contractor license revocation on his employment application produce net harm by depriving the hiring firm of material information needed to assess his trustworthiness, and does the downstream erosion of employer-employee trust once the revocation was discovered outweigh any benefit Engineer F gained by securing the position through a technically accurate but misleading answer?
From a consequentialist perspective, Engineer F's omission produced net harm across multiple dimensions. The immediate harm was informational: the hiring firm was deprived of material data needed to make an informed employment decision, potentially placing Engineer F in a role for which the firm would not have hired him had it known the full record. The downstream harm was relational: when the firm independently discovered the revocation, the trust foundation of the employment relationship was retroactively compromised - not only by the original misconduct but by the deliberate concealment, which is often more damaging to professional relationships than the underlying act. The systemic harm was institutional: if engineers are permitted to exploit narrow application wording to conceal adjudicated integrity violations, the reliability of professional employment disclosures as a screening mechanism is eroded for the entire profession. Against these harms, the benefit to Engineer F - securing a position he might not otherwise have obtained - is both self-interested and contingent on the concealment remaining undiscovered. A consequentialist calculus that accounts for discovery probability, relational harm, and systemic effects yields a clear verdict against the omission.
From a deontological perspective, does the NSPE Code's duty to act as a faithful agent and trustee impose on Engineer F an obligation to interpret the employment application's disciplinary question according to its evident purpose-assessing character and fitness-rather than its narrowest literal scope, such that omitting an adjudicated non-PE license revocation constitutes a breach of duty regardless of the question's precise wording?
From a deontological perspective, the NSPE Code's duty to act as a faithful agent and trustee does impose on Engineer F an obligation to interpret the employment application's disciplinary question according to its evident purpose rather than its narrowest literal scope. The faithful agent duty is not merely a duty to avoid active deception; it is an affirmative duty to serve the principal's legitimate informational interests. A hiring firm's evident purpose in asking about disciplinary history is to assess character and fitness - not to conduct a technical exercise in license-category taxonomy. An engineer who interprets such a question by its narrowest literal scope, knowing that the interpretation will produce a materially false impression, is not acting as a faithful agent; he is acting as an adversarial party seeking to minimize disclosure. The deontological duty of fidelity requires that Engineer F ask not 'what is the minimum I must disclose under the strictest reading of this question?' but rather 'what information does my principal need to make an informed decision?' The answer to the latter question clearly includes the contractor license revocation.
Question 14 Counterfactual
If Engineer F had voluntarily disclosed the contractor license revocation on the employment application before being hired, would the engineering firm have been ethically and practically better positioned to make an informed hiring decision, and would proactive disclosure have mitigated or eliminated the integrity concerns that arose when the firm independently discovered the omission?
Had Engineer F voluntarily disclosed the contractor license revocation on the employment application - ideally with a brief contextual explanation of the circumstances and any remedial steps taken - the engineering firm would have been materially better positioned to make an informed hiring decision, and the integrity concerns that arose upon independent discovery would have been substantially mitigated or eliminated. Proactive disclosure transforms the character signal from concealment to candor: an applicant who discloses an adverse history before being asked demonstrates the very honesty and self-awareness that a hiring firm seeks in a professional engineer. The firm might still have declined to hire Engineer F, but that outcome would reflect a legitimate exercise of informed judgment rather than a trust betrayal. More importantly, if the firm had hired Engineer F with full knowledge of the revocation, the subsequent discovery would carry no additional sting - there would be nothing to discover that was not already known. The ethical and practical case for proactive disclosure is therefore not merely deontological but prudential: it is the strategy most consistent with long-term professional integrity and relational trust.
Question 15 Counterfactual
If Engineer F's situation had involved only an unresolved allegation of contractor misconduct-rather than a formal adjudicated revocation-would the ethical obligation to disclose on the employment application have been different, and how does the allegation-versus-adjudication distinction drawn in BER Case 97-11 apply to calibrate the disclosure threshold between Engineer A's pending complaint and Engineer F's completed revocation proceeding?
If Engineer F's situation had involved only an unresolved allegation of contractor misconduct - rather than a formal adjudicated revocation - the ethical obligation to disclose on the employment application would have been materially different and would have required the kind of prudential weighing that the Board in BER Case 97-11 permitted Engineer A to perform. An unresolved allegation is, by definition, a contested claim whose truth has not been established by a competent authority; disclosing it risks conveying a false negative impression based on an accusation that may ultimately be unfounded. The allegation-versus-adjudication distinction is therefore not merely procedural but epistemically significant: adjudication produces a settled factual record that the engineer cannot in good faith treat as ambiguous, while a pending allegation remains genuinely uncertain. Engineer F's case involved a completed revocation proceeding - an authoritative determination that the misconduct occurred - which eliminates the epistemic uncertainty that justified Engineer A's more cautious approach. The disclosure threshold calibration suggested by the two cases is: pending unresolved allegations permit prudential non-disclosure; formally adjudicated findings require disclosure, particularly when the underlying conduct implicates professional integrity.
Question 16 Counterfactual
If the employment application had been drafted more broadly-asking whether the applicant had ever had any professional or occupational license suspended, revoked, or disciplined in any field-would Engineer F have been compelled to disclose the contractor license revocation, and does the firm's failure to draft such a comprehensive question share any moral responsibility for the informational gap that resulted?
If the employment application had been drafted more broadly - asking whether the applicant had ever had any professional or occupational license of any kind suspended, revoked, or disciplined - Engineer F would unambiguously have been compelled to disclose the contractor license revocation, and his failure to do so under such a question would have constituted an outright false statement rather than a misleading omission. The firm's failure to draft such a comprehensive question does reflect a due diligence gap, but that gap does not bear significant moral weight in distributing responsibility for the informational deficit. The ethical obligation to disclose material integrity information is not contingent on the questioner's drafting sophistication; it flows from the engineer's own affirmative duties under the Code. The firm's imprecise drafting created an opportunity for evasion that Engineer F exploited, but the exploitation itself - not the opportunity - is the ethical violation. A more comprehensive question would have eliminated the ambiguity Engineer F relied upon, but the absence of such a question did not create a moral permission to conceal.
Question 17 Counterfactual
If Engineer F's contractor license revocation had involved a domain entirely unrelated to engineering-such as a food service or real estate license-rather than fire sprinkler contracting, which directly implicates public safety and fire protection, would the ethical obligation to disclose on a professional engineering employment application be weaker, and does the safety-critical nature of fire protection work amplify the materiality of the revocation to the point where disclosure would be required even under a narrow reading of the application question?
If Engineer F's contractor license revocation had involved a domain entirely unrelated to engineering - such as a food service or real estate license - the ethical obligation to disclose on a PE employment application would be weaker, though not necessarily absent. The materiality of a non-PE license revocation to a PE employment application is a function of two variables: the character relevance of the underlying conduct and the domain relevance of the licensed activity. A food service license revocation for a health code violation speaks primarily to regulatory compliance in an unrelated field and carries limited character signal for PE fitness. A real estate license revocation for misrepresentation would carry stronger character relevance because it implicates honesty directly, even though the domain is unrelated. Engineer F's contractor license revocation in fire sprinkler contracting scores high on both variables: the underlying conduct - enabling unlicensed practice - directly implicates professional integrity norms shared across all licensed professions, and the domain - fire protection - is a safety-critical field whose public welfare stakes are directly analogous to those that PE licensure is designed to protect. The safety-critical nature of fire protection work amplifies the materiality of the revocation and supports disclosure even under a narrow reading of the application question.
Rich Analysis Results
View ExtractionCausal-Normative Links 4
Negative Disclosure Answer on Application
- Engineer F Contractor License Revocation Non-Disclosure Employment Application
- Engineer F Technically True Misleading Answer Employment Application
- Engineer F Adjudicated Misconduct Employment Application Disclosure
- Engineer F Employment Application Contractor License Revocation Proactive Disclosure
- Engineer F Employer Question Intent Broad Interpretation Failure
- Engineer F Ethics Beyond Minimum Employment Disclosure Failure
- Engineer F Domain-Relevance Amplified Fire Protection Disclosure Failure
- Engineer F Artfully Misleading Employment Application Answer
- Engineer F Personal Misconduct Ethics Code Jurisdiction Recognition Failure
- Engineer F Non-Engineering License Disciplinary History Employment Disclosure Failure
Non-Disclosure to Active Client (BER 97-11 Precedent)
- Engineer A Pending Complaint Limited Background Information Prudential Weighing BER 97-11
- Engineer F Qualifications Non-Misrepresentation Employment Application
Unlicensed Individual License Sharing
- Engineer F Contractor License Number Lending Prohibition Violation
- Contractor License Number Lending Prohibition Obligation
- Engineer F Non-Engineering Professional License Revocation Character Disclosure
Post-Hire Non-Disclosure of Revocation
- Engineer F Employer-Employee Trust Foundation Proactive Disclosure Failure
- Employer-Employee Trust Foundation Proactive Disclosure Obligation
- Engineer F Ethics Beyond Minimum Employment Disclosure Failure
- Ethics Beyond Minimum Employment Relationship Conduct Obligation
- Engineer F Adjudicated Misconduct Employment Application Disclosure Failure
- Engineer F Domain-Relevance Amplified Fire Protection Disclosure Failure
- Domain-Relevance Amplified Adjudicated Misconduct Disclosure Obligation
- Engineer F Ethics Code Supersession of Legalistic Minimum Employment Disclosure
Question Emergence 17
Triggering Events
- Contractor License Revocation
- Disciplinary Record Created
- PE_License_Non-Suspension_Outcome
Triggering Actions
- Unlicensed Individual License Sharing
- Negative Disclosure Answer on Application
Competing Warrants
- Domain-Relevance Amplification Applied to Engineer F Fire Protection Contractor Revocation Engineer F Domain-Relevance Amplified Fire Protection Disclosure Failure
- Licensure Integrity Implicated by Engineer F License Lending Public Welfare Paramount Invoked as Cross-Domain Character Standard for Engineer F
- Engineer F Non-Engineering License Disciplinary History Employment Disclosure Failure Safety-Domain Cross-License Integrity Heightened Disclosure Constraint
Triggering Events
- Contractor License Revocation
- PE_License_Non-Suspension_Outcome
- Engineer F Hired By Firm
- Disciplinary Record Created
Triggering Actions
- Negative Disclosure Answer on Application
- Post-Hire_Non-Disclosure_of_Revocation
Competing Warrants
- Personal Misconduct Ethics Code Jurisdiction Applied to Engineer F Contractor Revocation Employment Application Question Scope Fidelity Obligation
- Whole-Person Character Integrity Standard Applied to Engineer F Employment Application Engineer F Personal Misconduct Ethics Code Jurisdiction Recognition Failure
- BER 75-5 Whole-Person Integrity Standard Activation Engineer F Non-Engineering Professional License Revocation Character Disclosure
Triggering Events
- Contractor License Revocation
- Disciplinary Record Created
- Engineer F Hired By Firm
Triggering Actions
- Negative Disclosure Answer on Application
- Unlicensed Individual License Sharing
Competing Warrants
- Technically True But Misleading Statement Prohibition Applied to Engineer F Employment Application Employment Application Question Scope Fidelity Obligation
- Honesty in Professional Representations Invoked by Engineer F Employment Application Engineer F Technically True Misleading Answer Employment Application
- Ethics Code Higher Standard Than Legal Minimum Applied to Engineer F Employment Disclosure Engineer F Employer Question Intent Broad Interpretation Failure
Triggering Events
- Contractor License Revocation
- Disciplinary Record Created
- Engineer F Hired By Firm
Triggering Actions
- Negative Disclosure Answer on Application
Competing Warrants
- Employment Application Question Scope Fidelity Obligation
- Hiring Firm Broad-Scope Disciplinary Inquiry Due Diligence Obligation Engineer F Qualifications Non-Misrepresentation Employment Application
- Engineer F Employer Question Intent Broad Interpretation Failure Engineering Firm Hiring Authority Broad Disciplinary Inquiry Due Diligence
Triggering Events
- Engineer F Hired By Firm
- Contractor License Revocation
- Disciplinary Record Created
- Firm Discovers Revocation
Triggering Actions
- Post-Hire_Non-Disclosure_of_Revocation
- Negative Disclosure Answer on Application
Competing Warrants
- Employer-Employee Trust Foundation Proactive Disclosure Obligation
- Ethics Beyond Minimum Employment Relationship Conduct Obligation Engineer F Non-Engineering Professional License Revocation Character Disclosure
- Engineer F Ethics Code Supersession of Legalistic Minimum Employment Disclosure Engineer F Employer-Employee Trust Foundation Proactive Disclosure Failure
Triggering Events
- Contractor License Revocation
- Disciplinary Record Created
Triggering Actions
- Unlicensed Individual License Sharing
- Negative Disclosure Answer on Application
Competing Warrants
- Engineer F Non-Engineering Professional License Revocation Character Disclosure Whole-Person Character Integrity Standard Applied to Engineer F Employment Application
- Domain-Relevance Amplification of Disclosure Obligation Personal Misconduct Ethics Code Jurisdiction Applied to Engineer F Contractor Revocation
- Omission Materiality of Contractor License Revocation by Engineer F
Triggering Events
- Contractor License Revocation
- Disciplinary Record Created
- Engineer F Hired By Firm
Triggering Actions
- Negative Disclosure Answer on Application
Competing Warrants
- Employment Application Question Scope Fidelity Obligation Technically True But Misleading Statement Prohibition Applied to Engineer F Employment Application
- Honesty in Professional Representations Invoked by Engineer F Employment Application Engineer F Employer Question Intent Broad Interpretation Failure
- Engineer F Artfully Misleading Employment Application Answer Ethics Minimum Non-Sufficiency Employment Disclosure Constraint
Triggering Events
- Contractor License Revocation
- Disciplinary Record Created
- PE_License_Non-Suspension_Outcome
Triggering Actions
- Non-Disclosure_to_Active_Client_(BER_97-11_Precedent)
- Negative Disclosure Answer on Application
- Post-Hire_Non-Disclosure_of_Revocation
Competing Warrants
- Allegation-Adjudication Distinction Invoked in Engineer F vs Engineer A Comparison Prudential Disclosure Applied to Engineer A Client B Background Information Recommendation
- Engineer A Pending Complaint Limited Background Information Prudential Weighing BER 97-11
- BER 97-11 vs Present Case Allegation-Adjudication Threshold Differential Engineer F Allegation vs Adjudication Disclosure Threshold Application
Triggering Events
- Contractor License Revocation
- Disciplinary Record Created
- Engineer F Hired By Firm
Triggering Actions
- Negative Disclosure Answer on Application
- Post-Hire_Non-Disclosure_of_Revocation
Competing Warrants
- Domain-Relevance Amplification Applied to Engineer F Fire Protection Contractor Revocation Omission Materiality of Contractor License Revocation by Engineer F
- Engineer F Fire Protection Safety Domain Heightened Materiality Engineer F Domain-Relevance Amplified Fire Protection Disclosure Failure
- Public Welfare Paramount Invoked as Cross-Domain Character Standard for Engineer F NSPE Code of Ethics - Fundamental Canon 1 (Public Safety, Health, and Welfare)
Triggering Events
- Contractor License Revocation
- Disciplinary Record Created
- Engineer F Hired By Firm
- Firm Discovers Revocation
Triggering Actions
- Negative Disclosure Answer on Application
- Unlicensed Individual License Sharing
- Post-Hire_Non-Disclosure_of_Revocation
Competing Warrants
- Whole-Person Character Integrity Standard Applied to Engineer F Employment Application Employment Application Question Scope Fidelity Obligation
- Engineer F Privacy vs. Material Omission Tension Engineer F Employer-Employee Trust Foundation Proactive Disclosure Failure
- Prudential Disclosure Relational Self-Protection Applied to Engineer F Employer Relationship Engineer F Ethics-Exceeds-Minimum Employment Conduct Failure
Triggering Events
- Contractor License Revocation
- PE_License_Non-Suspension_Outcome
- Engineer F Hired By Firm
- Firm Discovers Revocation
- Disciplinary Record Created
Triggering Actions
- Negative Disclosure Answer on Application
- Post-Hire_Non-Disclosure_of_Revocation
Competing Warrants
- Engineer F Qualifications Non-Misrepresentation Employment Application
- Employment Application Question Scope Fidelity Obligation Ethics Beyond Minimum Employment Relationship Conduct Obligation
- Engineer F Technically True Misleading Answer Employment Application
Triggering Events
- Contractor License Revocation
- PE_License_Non-Suspension_Outcome
- Disciplinary Record Created
- Engineer F Hired By Firm
Triggering Actions
- Negative Disclosure Answer on Application
Competing Warrants
- Employment Application Question Scope Fidelity Obligation Employer Question Intent Broad Interpretation Disclosure Obligation
- Engineer F Faithful Agent Duty Non-Override by Legalistic Evasion Engineer F Employer Question Intent Broad Interpretation Failure
- Engineer F Ethics Code Supersession of Legalistic Minimum Employment Disclosure Engineer F Non-Engineering Professional License Revocation Character Disclosure
Triggering Events
- Contractor License Revocation
- Engineer F Hired By Firm
- Firm Discovers Revocation
- Disciplinary Record Created
Triggering Actions
- Negative Disclosure Answer on Application
- Post-Hire_Non-Disclosure_of_Revocation
Competing Warrants
- Employment Application Question Scope Fidelity Obligation
- Employer-Employee Trust Foundation Proactive Disclosure Obligation Engineer F Privacy vs. Material Omission Tension
- Prudential Disclosure Relational Self-Protection Applied to Engineer F Employer Relationship
Triggering Events
- Contractor License Revocation
- Engineer F Hired By Firm
- Disciplinary Record Created
- PE_License_Non-Suspension_Outcome
Triggering Actions
- Negative Disclosure Answer on Application
Competing Warrants
- Hiring Firm Broad-Scope Disciplinary Inquiry Due Diligence Obligation
- Engineering Firm Hiring Authority Broad Disciplinary Inquiry Due Diligence Employer Question Intent Broad Interpretation Disclosure Obligation
- Engineer F Cross-Domain License Revocation Non-Disclosure Employment Application Constraint Engineering Firm Hiring Broad Disciplinary Inquiry Drafting Constraint
Triggering Events
- Contractor License Revocation
- PE_License_Non-Suspension_Outcome
- Engineer F Hired By Firm
- Disciplinary Record Created
Triggering Actions
- Negative Disclosure Answer on Application
- Unlicensed Individual License Sharing
- Post-Hire_Non-Disclosure_of_Revocation
Competing Warrants
- Employment Application Contractor License Revocation Proactive Disclosure Obligation Engineer F Non-Engineering License Disciplinary History Employment Disclosure Failure
- Domain-Relevance Amplified Adjudicated Misconduct Disclosure Obligation Engineer F Cross-Domain License Revocation Non-Disclosure Employment Application Constraint
- Whole-Person Character Integrity Standard Applied to Engineer F Employment Application Employment Application Question Scope Fidelity Obligation
- Engineer F Fire Protection Domain Safety Heightened Disclosure Materiality Engineer F Privacy vs. Material Omission Tension
Triggering Events
- Contractor License Revocation
- PE_License_Non-Suspension_Outcome
- Firm Discovers Revocation
- Engineer F Hired By Firm
- Disciplinary Record Created
Triggering Actions
- Negative Disclosure Answer on Application
- Non-Disclosure_to_Active_Client_(BER_97-11_Precedent)
- Post-Hire_Non-Disclosure_of_Revocation
Competing Warrants
- Engineer A Pending Complaint Limited Background Information Prudential Weighing BER 97-11
- BER 97-11 vs Present Case Allegation-Adjudication Threshold Differential Engineer F BER 97-11 Allegation vs Adjudication Disclosure Threshold Distinction
- Engineer F Ethics Code Supersession of Legalistic Minimum Employment Disclosure Engineer F Allegation vs Adjudication Disclosure Threshold Application
- Employer-Employee Trust Foundation Proactive Disclosure Obligation Engineer F Privacy vs Material Omission Tension
Triggering Events
- Contractor License Revocation
- PE_License_Non-Suspension_Outcome
- Engineer F Hired By Firm
- Disciplinary Record Created
- Firm Discovers Revocation
Triggering Actions
- Negative Disclosure Answer on Application
- Post-Hire_Non-Disclosure_of_Revocation
- Unlicensed Individual License Sharing
Competing Warrants
- Employment Application Question Scope Fidelity Obligation
- Engineer F Non-Engineering Professional License Revocation Character Disclosure Engineer F Privacy vs. Material Omission Tension
- Whole-Person Character Integrity Standard in Engineering Employment Cross-License Disciplinary Disclosure Scope Invoked by Engineer F Application
- Personal Misconduct Ethics Code Jurisdiction Applied to Engineer F Contractor Revocation Engineer F Contractor License Number Lending Prohibition Violation
Resolution Patterns 22
Determinative Principles
- Allegation-Adjudication Distinction: adjudication is a sufficient condition for disclosure because it eliminates the evidentiary uncertainty that justified Engineer A's more cautious approach
- Prudential Disclosure principle: unresolved allegations permit weighing of disclosure risks because their truth remains contested, but this weighing is foreclosed once adjudication occurs
- Spectrum of intermediate findings: the distinction is evidentiary and graduated, not binary, requiring case-by-case materiality analysis for consent orders, settlements, and deferred revocations
Determinative Facts
- Engineer F faced a formally adjudicated revocation — a finding of fact by a competent authority — not a pending or unresolved allegation
- Engineer A in BER 97-11 faced an unresolved complaint whose truth was contested and whose disclosure could itself cause harm, justifying a more cautious prudential approach
- Adjudication eliminates the uncertainty that grounded Engineer A's permitted weighing and replaces it with a settled factual record the engineer cannot in good faith treat as ambiguous
Determinative Principles
- Domain-Relevance Amplification: materiality of a non-PE license revocation is amplified when the prior domain is safety-critical
- Character Relevance: the underlying conduct must implicate honesty and integrity norms shared across licensed professions
- Omission Materiality: the significance of omitted information is calibrated to both character signal and domain proximity
Determinative Facts
- Engineer F's contractor license was revoked specifically for enabling unlicensed practice in fire sprinkler contracting — a safety-critical field directly analogous to PE public-welfare obligations
- The underlying conduct (lending his license number to an unrelated unlicensed individual) directly implicates professional integrity norms, not merely a regulatory technicality
- Fire protection is a life-safety domain whose public welfare stakes mirror those that PE licensure is designed to protect, closing the domain-relevance gap
Determinative Principles
- Allegation-Adjudication Distinction: formally adjudicated findings produce a settled factual record that eliminates the epistemic uncertainty justifying prudential non-disclosure
- Omission Materiality: adjudicated findings of integrity violations cross a materiality threshold that makes non-disclosure an ethics violation
- Prudential Disclosure: pending unresolved allegations permit weighing of disclosure risks, but this latitude does not extend to completed revocation proceedings
Determinative Facts
- Engineer F's contractor license revocation was a completed, formal governmental adjudication — not a pending or unresolved allegation
- BER Case 97-11 involved only a pending ethics complaint against Engineer A, which the board treated as epistemically uncertain and therefore subject to prudential weighing
- The adjudicated finding established that Engineer F committed a specific integrity violation, eliminating any good-faith claim of ambiguity about whether the misconduct occurred
Determinative Principles
- Technically True But Misleading Statement Prohibition: an answer that is literally accurate but suppresses material integrity-relevant information violates the ethics code
- Evident Purpose Interpretation: engineers must interpret application questions according to their evident purpose — assessing character and fitness — rather than their most self-serving literal reading
- Employment Application Question Scope Fidelity is a subordinate principle that yields when the omitted information is both material and reflects an adjudicated integrity finding
Determinative Facts
- The application question was narrowly worded to reference only PE license discipline, but its evident purpose was to assess the applicant's character and fitness for professional trust
- Engineer F answered 'no' to the disciplinary question despite holding a formally adjudicated contractor license revocation for an integrity violation
- The narrow drafting was exploited by Engineer F to suppress a material adjudicated finding, which the board treated as the operative ethical wrong rather than a permissible reliance on literal scope
Determinative Principles
- Allegation-Adjudication Distinction: the disclosure threshold is calibrated to epistemic certainty and adjudicative finality, not to a binary always/never rule
- Omission Materiality (adjudicated findings) takes precedence over Prudential Disclosure (allegations) as the operative principle once adjudicative finality is established
- Moral Responsibility Allocation: the engineer's responsibility for the informational gap increases as the certainty and severity of the undisclosed finding increases, diminishing the firm's drafting imprecision as a mitigating factor
Determinative Facts
- Engineer F's revocation was a completed formal governmental determination, placing it in the adjudicated-findings regime where disclosure is categorically required rather than prudentially weighed
- BER Case 97-11 involved a pending, unresolved ethics complaint against Engineer A — an epistemically uncertain allegation — which the board treated as subject to prudential weighing rather than categorical disclosure
- The firm's narrow application drafting created an informational gap, but the board held that moral responsibility for that gap shifts decisively to Engineer F as the certainty and integrity-relevance of the undisclosed finding increases
Determinative Principles
- Honesty and integrity govern all professional relations, not merely narrowly defined engineering acts
- Technically accurate but misleading omissions violate the prohibition on deceptive acts
- Engineers must not obtain employment through misrepresentation or material omission
Determinative Facts
- Engineer F answered 'no' to the employment application's disciplinary question despite having had his contractor's license formally revoked
- The revocation was an adjudicated outcome of a formal proceeding, not a mere allegation or administrative lapse
- The employment application's evident purpose was to assess character and fitness, making the revocation material regardless of the question's precise wording
Determinative Principles
- The ethical weight of a disclosure obligation scales with the character relevance of the underlying conduct, not merely with the formal fact of adjudication
- Administrative or technical violations speak to organizational competence and may fall below the materiality threshold for mandatory disclosure on a PE employment application
- Deliberately lending a license number to an unrelated unlicensed individual is an affirmative act of deception that sits at the core of what the Code's integrity provisions address
Determinative Facts
- Engineer F's contractor license was revoked specifically for allowing an unlicensed individual unrelated to his firm to use his contractor license number — an affirmative integrity-implicating act, not a paperwork lapse
- The conduct directly undermined the licensing system designed to protect the public, implicating the same professional integrity norms that govern PE licensure
- A purely administrative revocation — such as failure to renew on time — would not necessarily implicate the honesty, trustworthiness, or professional integrity that the Code's whole-person character standard is designed to assess
Determinative Principles
- Technically accurate but misleading answers are ethically prohibited when they exploit imprecise drafting to conceal material information
- The evident purpose of a question governs its ethical scope, not its narrowest literal wording
- The duty of candor rests with the applicant, not with the sophistication of the questioner
Determinative Facts
- The employment application question referenced discipline 'in the practice of professional engineering,' which Engineer F used to justify omitting the contractor license revocation
- The contractor license revocation was an adjudicated integrity violation, not a pending allegation or minor administrative matter
- The evident purpose of the disciplinary question was to assess character and fitness for professional trust, not merely to audit PE license status
Determinative Principles
- The allegation-adjudication distinction creates a meaningful threshold: adjudicated findings trigger disclosure obligations while unresolved allegations may not
- A continuing duty of candor as faithful agent and trustee persists throughout the employment relationship, not only at the moment of application
- An engineer cannot invoke reputational-harm or uncertainty rationales to justify withholding a formally determined fact about their own character
Determinative Facts
- Engineer F's contractor license revocation was a completed adjudication, distinguishing it from the pending unresolved complaint in BER Case 97-11
- Once hired, Engineer F's employer was operating under a materially incomplete understanding of his professional history that Engineer F himself had created
- The continuing employment relationship — including project assignments, supervisory authority, and client representations — made the undisclosed revocation an ongoing material omission
Determinative Principles
- The ethical obligation to disclose material integrity information flows from the engineer's own Code duties, not from the precision of the questioner's drafting
- Legalistic exploitation of imprecisely worded questions to conceal adjudicated integrity violations is explicitly prohibited by the Code
- The firm's imperfect drafting constitutes a due diligence gap but does not constitute a moral license for the applicant to withhold material information
Determinative Facts
- The hiring firm failed to draft a comprehensive disciplinary inquiry question covering all professional or occupational licenses
- Engineer F exploited the narrow wording of the question as a justification for omitting the contractor license revocation
- Any reasonable employer would consider an adjudicated integrity violation material to a hiring decision regardless of the license domain involved
Determinative Principles
- The faithful agent and trustee duty creates a fiduciary-adjacent continuing obligation of candor that persists throughout the employment relationship
- Silence in the face of a known material omission, once an employment relationship is established, compounds rather than cures the original ethical breach
- The disclosure obligation crystallizes when the employer's reliance on the incomplete record becomes consequential
Determinative Facts
- Once hired, Engineer F's employer was operating under a materially incomplete understanding of his professional history that Engineer F himself had created through omission
- Engineer F's assignment to projects, grant of supervisory authority, or representation to clients as a qualified professional made the employer's reliance on the incomplete record consequential
- The original omission on the application did not discharge the ongoing duty — it created a continuing state of material non-disclosure within the employment relationship
Determinative Principles
- Domain-Relevance Amplification: misconduct in a safety-critical licensed domain heightens, not merely equals, disclosure materiality
- Cross-domain integrity relevance: subverting one licensing system speaks directly to fitness in another
- Public safety primacy: fire sprinkler systems are life-safety infrastructure, making the violation substantive rather than technical
Determinative Facts
- Engineer F lent his contractor license number to an unlicensed individual, enabling unlicensed practice in fire sprinkler contracting
- Fire sprinkler systems are classified as life-safety infrastructure, making the domain safety-critical rather than administratively routine
- The contractor license revocation was formally adjudicated, not merely alleged, establishing a settled factual record of the integrity violation
Determinative Principles
- Prohibition on technically true but misleading statements: literal accuracy does not satisfy the Code if the overall impression conveyed is false
- Evident purpose doctrine: the question must be interpreted according to its functional intent — assessing adjudicated professional misconduct — not its narrowest grammatical scope
- Material omission standard: withholding information that would predictably alter the recipient's assessment constitutes a deceptive act regardless of literal accuracy
Determinative Facts
- The employment application's disciplinary question was drafted narrowly, referencing only PE license discipline, but its evident purpose was to surface any adjudicated professional misconduct bearing on fitness
- Engineer F answered 'no,' which was technically accurate as to PE license discipline but functionally conveyed to the hiring firm that no relevant disciplinary history existed
- An adjudicated contractor license revocation for an integrity violation in a safety-critical domain did in fact exist and was withheld
Determinative Principles
- Whole-Person Character Integrity Standard: the Code's ethical scrutiny extends to non-engineering conduct when that conduct bears on honesty, integrity, and public safety
- Cross-domain character relevance as jurisdictional trigger: the operative question is not where the conduct occurred but whether it is relevant to PE fitness
- Bounded jurisdictional principle: the Code does not reach genuinely private conduct unrelated to professional integrity, preventing over-extension
Determinative Facts
- Engineer F's contractor license revocation arose outside his PE role but implicated the same integrity norms — prohibition on enabling unlicensed practice, licensing system integrity, public safety — that PE ethics enforces
- The revocation was not a private personal matter but an adjudicated finding by a competent licensing authority in a regulated professional domain
- The conduct (lending a license number to enable unlicensed practice) directly parallels the kinds of integrity violations the PE code is designed to prevent
Determinative Principles
- Kantian duty of non-deception: truthfulness requires not merely literal accuracy but that statements not be designed to produce false beliefs in the recipient's mind
- Universalizability test: a maxim permitting engineers to answer disciplinary questions by the narrowest literal reading would, if universalized, render employment application disclosure meaningless
- Faithful agent duty interpreted through evident purpose: the duty to act as a faithful agent requires interpreting disclosure questions according to their evident purpose — assessing character and fitness — not their narrowest grammatical scope
Determinative Facts
- Engineer F's 'no' answer was technically accurate as to PE license discipline but was crafted to exploit the question's narrow wording in a way that would predictably cause the hiring firm to believe no relevant disciplinary history existed
- An adjudicated contractor license revocation for an integrity violation in a safety-critical domain existed and was withheld, constituting a deception by omission
- The employment application's disciplinary question had the evident purpose of assessing whether the applicant had a history of adjudicated professional misconduct bearing on fitness for a PE role
Determinative Principles
- Whole-Person Character Integrity Standard: honesty and integrity as stable virtues extend beyond narrow professional role boundaries
- Rejection of legalistic self-protection: scanning a question for its narrowest defensible reading to withhold material information is incompatible with genuine virtue
- Good character standard: a person of good character acts on the questioner's evident purpose, not the question's minimum literal scope
Determinative Facts
- Engineer F deliberately relied on the narrow wording of the employment application question rather than its evident purpose of assessing fitness and integrity
- The contractor license revocation was an adjudicated integrity violation — not a mere allegation or administrative lapse — making it plainly material to a character assessment
- The hiring firm's evident purpose in asking about disciplinary history was to assess whole-person fitness, a purpose Engineer F recognized and exploited a drafting gap to circumvent
Determinative Principles
- Net harm calculus: consequentialist analysis aggregates immediate informational harm, downstream relational harm, and systemic institutional harm against Engineer F's self-interested benefit
- Discovery probability and relational trust: concealment that is later independently discovered compounds harm beyond the original omission
- Systemic erosion principle: permitting exploitation of narrow application wording degrades professional employment disclosures as a screening mechanism for the entire profession
Determinative Facts
- The hiring firm was deprived of material data needed to make an informed employment decision, potentially placing Engineer F in a role he would not have been offered with full disclosure
- The firm independently discovered the revocation, retroactively compromising the trust foundation of the employment relationship — with the concealment itself more damaging than the underlying act
- Engineer F's benefit — securing the position — was both self-interested and contingent on the concealment remaining undiscovered, making it a fragile and ethically weightless counterweight
Determinative Principles
- Faithful agent and trustee duty: the NSPE Code's affirmative obligation to serve the principal's legitimate informational interests, not merely to avoid active deception
- Evident purpose standard: a disciplinary question on an employment application must be interpreted according to its evident purpose — assessing character and fitness — not its narrowest literal taxonomy
- Adversarial versus fiduciary posture: an engineer who minimizes disclosure by exploiting drafting gaps is acting as an adversarial party, not as a faithful agent
Determinative Facts
- The employment application's disciplinary question was drafted narrowly to reference professional engineering license discipline, but its evident purpose was plainly to assess character and fitness across the applicant's full professional history
- Engineer F interpreted the question by its narrowest literal scope with knowledge that this interpretation would produce a materially false impression in the hiring firm's mind
- The contractor license revocation was an adjudicated integrity violation directly relevant to the faithful agent duty, making it precisely the kind of information a principal needs to make an informed decision
Determinative Principles
- Proactive disclosure transforms the character signal: voluntary disclosure before being asked demonstrates honesty and self-awareness rather than concealment
- Prudential disclosure principle: proactive disclosure is the strategy most consistent with long-term professional integrity and relational trust, independent of deontological obligation
- Informed consent of the hiring firm: disclosure enables a legitimate exercise of informed judgment rather than a trust betrayal, regardless of the hiring outcome
Determinative Facts
- Had Engineer F disclosed the revocation proactively — ideally with contextual explanation and remedial steps — the firm would have been materially better positioned to make an informed hiring decision
- The firm's independent discovery of the concealed revocation created a compounded trust injury — the concealment itself became a second integrity concern layered on top of the original revocation
- If the firm had hired Engineer F with full knowledge, subsequent discovery would carry no additional sting because there would be nothing new to discover, eliminating the relational harm entirely
Determinative Principles
- Ethical obligation is not contingent on drafting sophistication: the engineer's affirmative disclosure duty flows from the Code, not from the questioner's ability to draft a comprehensive question
- Opportunity versus permission distinction: the firm's imprecise drafting created an opportunity for evasion, but the exploitation of that opportunity — not the opportunity itself — is the ethical violation
- Moral responsibility distribution: the firm's due diligence gap does not bear significant moral weight in distributing responsibility for the informational deficit
Determinative Facts
- A more broadly drafted question — asking about any professional or occupational license of any kind — would have unambiguously compelled disclosure and rendered Engineer F's omission an outright false statement rather than a misleading omission
- The firm's failure to draft a comprehensive question reflects a due diligence gap, but that gap did not create a moral permission for Engineer F to conceal a material adjudicated integrity violation
- Engineer F exploited the drafting gap deliberately, meaning the informational deficit resulted from his active choice to rely on narrow wording rather than from any passive ambiguity
Determinative Principles
- Whole-Person Character Integrity Standard: the ethics code's scrutiny extends to non-engineering conduct when that conduct directly implicates the same integrity norms the code exists to enforce
- Domain-Relevance Amplification: the safety-critical nature of fire sprinkler contracting closes any residual gap between the contractor domain and the PE ethics domain
- Integrity Norm Mirroring: Engineer F's act of lending his license number to an unlicensed individual mirrors paradigmatic engineering ethics violations — misrepresentation of qualifications, facilitation of unlicensed practice, and endangerment of public safety
Determinative Facts
- Engineer F lent his contractor license number to an unrelated unlicensed individual, an act that directly mirrors the integrity violations the PE ethics code is designed to prevent
- The revocation arose in fire sprinkler contracting — a safety-sensitive domain — which amplifies its materiality and closes the domain-boundedness objection
- The revocation was formally adjudicated, establishing that the integrity violation was not merely alleged but authoritatively confirmed
Determinative Principles
- The character of the underlying misconduct—an affirmative integrity violation—heightens the disclosure obligation beyond what a purely technical or administrative license deficiency would trigger
- Domain-relevance amplification: misconduct in a safety-critical field (fire sprinkler contracting) mirrors the public-safety stakes that animate engineering ethics, intensifying materiality
- Adjudicated findings create a categorically stronger disclosure obligation than unresolved allegations, establishing a threshold above mere prudential disclosure
Determinative Facts
- Engineer F's revocation arose from deliberately allowing an unlicensed individual unrelated to his firm to use his contractor license number—an affirmative integrity violation, not a procedural lapse
- The misconduct was resolved through a formal adjudicated proceeding, distinguishing it from the unresolved complaint in BER 97-11 and placing it above the allegation-versus-adjudication threshold
- Fire sprinkler contracting is a safety-sensitive domain whose public-protection stakes directly parallel those underlying PE licensure ethics, amplifying the materiality of the revocation
Decision Points
View ExtractionShould Engineer F disclose the contractor license revocation on the employment application, or answer 'no' based on the question's literal limitation to PE license discipline?
- Disclose Revocation With Contextual Explanation
- Answer No Based on Literal Question Scope
- Seek Clarification Before Answering
Should Engineer F proactively disclose the contractor license revocation to his employer after being hired, or treat the omission as closed once the application was submitted and the narrow question technically answered?
- Disclose Proactively Upon Employment Commencement
- Disclose Only If Directly Assigned to Fire Protection Work
- Treat Application Answer as Closing Disclosure Obligation
Should the board treat Engineer F's adjudicated contractor license revocation as categorically requiring disclosure — distinguishing it from the mere allegation Engineer A faced in BER 97-11 — or apply the same prudential weighing standard that permitted Engineer A to exercise discretion about disclosure?
- Apply Categorical Disclosure Obligation for Adjudicated Findings
- Apply BER 97-11 Prudential Weighing Standard
- Apply Graduated Standard Based on Domain Proximity
Should Engineer F disclose the contractor license revocation on the employment application despite the question's narrow wording, or answer 'no' on the ground that the question literally covers only PE license discipline?
- Disclose Revocation With Contextual Explanation
- Answer No Based on Literal Question Scope
- Disclose Only If Directly Asked About Contractor Licenses
After being hired without disclosing the contractor license revocation, should Engineer F proactively inform his employer of the revocation, or remain silent unless the employer independently discovers it?
- Proactively Disclose Revocation to Employer
- Remain Silent Unless Directly Questioned
- Disclose Only Upon Relevant Project Assignment
Should the engineering firm interpret its employment application disciplinary question according to its evident purpose — capturing any adjudicated professional misconduct — or accept that its narrow literal drafting confined Engineer F's disclosure obligation to PE license matters only?
- Interpret Question by Evident Purpose, Hold Engineer Responsible
- Accept Narrow Drafting as Defining Disclosure Scope
- Share Responsibility and Revise Application Prospectively
Should Engineer F disclose the contractor license revocation on the employment application despite the question's narrow wording referencing only professional engineering license discipline, or answer 'no' based on the question's literal scope?
- Disclose Revocation with Contextual Explanation
- Answer 'No' Based on Literal Question Scope
- Seek Clarification Before Answering
Should Engineer F proactively disclose the contractor license revocation to his employer after being hired, or maintain silence on the grounds that the employment relationship has already been established and no new triggering event has occurred?
- Proactively Disclose Revocation to Employer
- Disclose Only If Directly Assigned to Fire Protection Work
- Maintain Silence Absent Direct Employer Inquiry
Should the Engineering Firm Hiring Authority disclose Engineer F's adjudicated contractor license revocation to relevant parties — such as clients, project teams, or licensing authorities — upon discovering it, or treat the matter as an internal employment issue requiring no external disclosure?
- Disclose to Affected Clients and Assess Regulatory Reporting
- Take Internal Corrective Action Only
- Conduct Project-by-Project Safety Risk Assessment Before Disclosing
Should Engineer F disclose the contractor license revocation on the employment application despite the question's narrow wording referencing only PE license discipline, or rely on the literal scope of the question to justify omitting the revocation?
- Disclose Revocation Voluntarily with Context
- Answer Literally Within Question's Stated Scope
- Seek Clarification Before Answering
After being hired without disclosing the contractor license revocation, should Engineer F proactively disclose the revocation to his employer, or maintain silence on the grounds that the application process has concluded and no new triggering event has occurred?
- Disclose Proactively to Employer Post-Hire
- Disclose Only If Directly Assigned to Relevant Work
- Maintain Silence as Application Process Concluded
Should Engineer F treat the adjudicated contractor license revocation as triggering a categorical, non-waivable disclosure obligation on the employment application — foreclosing any prudential weighing — or apply the same discretionary balancing that BER 97-11 permitted Engineer A to perform regarding an unresolved allegation?
- Treat Adjudication as Categorical Disclosure Trigger
- Apply Prudential Weighing as in BER 97-11
- Disclose Only If Domain Directly Matches Employer Work
Case Narrative
Phase 4 narrative construction results for Case 148
Opening Context
You are Engineer A, a practicing engineer retained to provide design and scheduling services on an active project—a role that carries both technical responsibility and professional accountability. Unbeknownst to your current client, a former client has filed an ethics complaint against you alleging professional incompetence, a matter you have chosen not to disclose despite your ongoing engagement. As the case unfolds against a backdrop of contractor license revocations, adjudicated wrongdoing, and complex cross-domain disclosure obligations, the boundaries of your professional duty are about to be tested.
Characters (6)
A licensed PE and former contracting firm owner whose contractor's license was revoked for improperly lending his license number, who then omitted this disciplinary history on a subsequent engineering employment application.
- Likely motivated by self-preservation and career advancement, calculating that the revocation of a contractor's license — distinct from his PE license — fell outside the spirit of the application question and would not surface during hiring review.
A professional engineering employer that administered a disciplinary disclosure question on its employment application and later discovered through independent means that a candidate had concealed a contractor's license revocation.
- Motivated to protect the firm's professional reputation, liability exposure, and ethical standing by ensuring that hired engineers meet standards of honesty and full disclosure, prompting scrutiny once the omission came to light.
A practicing engineer retained for design and scheduling services who faced a pending ethics complaint from a former client alleging incompetence but chose not to proactively inform his current client of that complaint.
- Likely motivated by a desire to protect his professional reputation and retain the current engagement, judging — perhaps reasonably but imperfectly — that an unresolved, unproven complaint did not rise to the level of mandatory disclosure.
A client who retained Engineer A for manufacturing facility design and scheduling services and felt blindsided upon learning through a third party about a pending ethics complaint against their engineer.
- Motivated by a reasonable expectation of transparency and informed decision-making, believing that material information about an engineer's professional standing directly affects trust, project risk assessment, and the client's ability to make an educated retention decision.
Client C had previously engaged Engineer A for similar services and filed an ethics complaint with the state board alleging Engineer A lacked competence to perform those services.
Engineer F's employer asked Engineer F specifically about whether Engineer F had a license suspended or been disciplined in connection with the practice of professional engineering. The employer's question, while narrowly worded, sought to elicit information about Engineer F's character, integrity, and credibility as a professional engineer.
States (10)
Event Timeline (25)
| # | Event | Type |
|---|---|---|
| 1 | The case centers on Engineer F, a licensed professional engineer whose contractor's license was revoked by state authorities, setting the stage for a series of ethical violations involving dishonesty and failure to uphold professional responsibilities. | state |
| 2 | Drawing on the precedent established in BER 97-11, Engineer F failed to disclose material information to an active client, violating the foundational ethical obligation that engineers must be transparent and forthright with those they are currently serving. | action |
| 3 | Engineer F allowed an unlicensed individual to operate under their professional engineering license, a serious ethical and legal breach that undermines public safety and the integrity of the licensure system designed to ensure qualified oversight. | action |
| 4 | When completing a professional application, Engineer F answered negatively to a disclosure question — likely regarding prior disciplinary action — misrepresenting their professional history and deceiving the reviewing authority from the outset. | action |
| 5 | After being hired by a firm, Engineer F continued to conceal the fact that their contractor's license had been revoked, denying the employer information that was directly relevant to their professional standing and fitness for the role. | action |
| 6 | State authorities formally revoked Engineer F's contractor's license, representing an official disciplinary action that established a documented record of professional misconduct and triggered the subsequent chain of ethical failures. | automatic |
| 7 | Despite the contractor's license revocation, Engineer F's professional engineering (PE) license was not suspended, a significant outcome that raised questions about the adequacy of cross-disciplinary accountability within the professional licensing system. | automatic |
| 8 | Engineer F's employing firm eventually discovered the previously concealed contractor's license revocation, a pivotal moment that exposed the sustained pattern of dishonesty and prompted a formal ethical review of Engineer F's conduct. | automatic |
| 9 | Engineer F Hired By Firm | automatic |
| 10 | Disciplinary Record Created | automatic |
| 11 | Tension between Employment Application Contractor License Revocation Proactive Disclosure Obligation and Ethics Minimum Non-Sufficiency Employment Disclosure Constraint | automatic |
| 12 | Tension between Employer-Employee Trust Foundation Proactive Disclosure Obligation and Safety-Domain Cross-License Integrity Heightened Disclosure Constraint | automatic |
| 13 | Should Engineer F disclose the contractor license revocation on the employment application, or answer 'no' based on the question's literal limitation to PE license discipline? | decision |
| 14 | Should Engineer F proactively disclose the contractor license revocation to his employer after being hired, or treat the omission as closed once the application was submitted and the narrow question technically answered? | decision |
| 15 | Should the board treat Engineer F's adjudicated contractor license revocation as categorically requiring disclosure — distinguishing it from the mere allegation Engineer A faced in BER 97-11 — or apply the same prudential weighing standard that permitted Engineer A to exercise discretion about disclosure? | decision |
| 16 | Should Engineer F disclose the contractor license revocation on the employment application despite the question's narrow wording, or answer 'no' on the ground that the question literally covers only PE license discipline? | decision |
| 17 | After being hired without disclosing the contractor license revocation, should Engineer F proactively inform his employer of the revocation, or remain silent unless the employer independently discovers it? | decision |
| 18 | Should the engineering firm interpret its employment application disciplinary question according to its evident purpose — capturing any adjudicated professional misconduct — or accept that its narrow literal drafting confined Engineer F's disclosure obligation to PE license matters only? | decision |
| 19 | Should Engineer F disclose the contractor license revocation on the employment application despite the question's narrow wording referencing only professional engineering license discipline, or answer 'no' based on the question's literal scope? | decision |
| 20 | Should Engineer F proactively disclose the contractor license revocation to his employer after being hired, or maintain silence on the grounds that the employment relationship has already been established and no new triggering event has occurred? | decision |
| 21 | Should the Engineering Firm Hiring Authority disclose Engineer F's adjudicated contractor license revocation to relevant parties — such as clients, project teams, or licensing authorities — upon discovering it, or treat the matter as an internal employment issue requiring no external disclosure? | decision |
| 22 | Should Engineer F disclose the contractor license revocation on the employment application despite the question's narrow wording referencing only PE license discipline, or rely on the literal scope of the question to justify omitting the revocation? | decision |
| 23 | After being hired without disclosing the contractor license revocation, should Engineer F proactively disclose the revocation to his employer, or maintain silence on the grounds that the application process has concluded and no new triggering event has occurred? | decision |
| 24 | Should Engineer F treat the adjudicated contractor license revocation as triggering a categorical, non-waivable disclosure obligation on the employment application — foreclosing any prudential weighing — or apply the same discretionary balancing that BER 97-11 permitted Engineer A to perform regarding an unresolved allegation? | decision |
| 25 | The Board's conclusion implicitly rejects the argument that Engineer F could ethically rely on the narrow literal wording of the employment application question — which referenced only discipline 'in | outcome |
Decision Moments (12)
- Disclose Revocation With Contextual Explanation Actual outcome
- Answer No Based on Literal Question Scope
- Seek Clarification Before Answering
- Disclose Proactively Upon Employment Commencement Actual outcome
- Disclose Only If Directly Assigned to Fire Protection Work
- Treat Application Answer as Closing Disclosure Obligation
- Apply Categorical Disclosure Obligation for Adjudicated Findings Actual outcome
- Apply BER 97-11 Prudential Weighing Standard
- Apply Graduated Standard Based on Domain Proximity
- Disclose Revocation With Contextual Explanation Actual outcome
- Answer No Based on Literal Question Scope
- Disclose Only If Directly Asked About Contractor Licenses
- Proactively Disclose Revocation to Employer Actual outcome
- Remain Silent Unless Directly Questioned
- Disclose Only Upon Relevant Project Assignment
- Interpret Question by Evident Purpose, Hold Engineer Responsible Actual outcome
- Accept Narrow Drafting as Defining Disclosure Scope
- Share Responsibility and Revise Application Prospectively
- Disclose Revocation with Contextual Explanation Actual outcome
- Answer 'No' Based on Literal Question Scope
- Seek Clarification Before Answering
- Proactively Disclose Revocation to Employer Actual outcome
- Disclose Only If Directly Assigned to Fire Protection Work
- Maintain Silence Absent Direct Employer Inquiry
- Disclose to Affected Clients and Assess Regulatory Reporting Actual outcome
- Take Internal Corrective Action Only
- Conduct Project-by-Project Safety Risk Assessment Before Disclosing
- Disclose Revocation Voluntarily with Context Actual outcome
- Answer Literally Within Question's Stated Scope
- Seek Clarification Before Answering
- Disclose Proactively to Employer Post-Hire Actual outcome
- Disclose Only If Directly Assigned to Relevant Work
- Maintain Silence as Application Process Concluded
- Treat Adjudication as Categorical Disclosure Trigger Actual outcome
- Apply Prudential Weighing as in BER 97-11
- Disclose Only If Domain Directly Matches Employer Work
Sequential action-event relationships. See Analysis tab for action-obligation links.
- Non-Disclosure_to_Active_Client_(BER_97-11_Precedent) Unlicensed Individual License Sharing
- Unlicensed Individual License Sharing Negative Disclosure Answer on Application
- Negative Disclosure Answer on Application Post-Hire_Non-Disclosure_of_Revocation
- Post-Hire_Non-Disclosure_of_Revocation Contractor License Revocation
- conflict_1 decision_1
- conflict_1 decision_2
- conflict_1 decision_3
- conflict_1 decision_4
- conflict_1 decision_5
- conflict_1 decision_6
- conflict_1 decision_7
- conflict_1 decision_8
- conflict_1 decision_9
- conflict_1 decision_10
- conflict_1 decision_11
- conflict_1 decision_12
- conflict_2 decision_1
- conflict_2 decision_2
- conflict_2 decision_3
- conflict_2 decision_4
- conflict_2 decision_5
- conflict_2 decision_6
- conflict_2 decision_7
- conflict_2 decision_8
- conflict_2 decision_9
- conflict_2 decision_10
- conflict_2 decision_11
- conflict_2 decision_12
Key Takeaways
- Engineers have an affirmative ethical duty to disclose material information bearing on their character and fitness that goes beyond the literal scope of application questions, particularly when omission would create a misleading impression.
- A license revocation in any professional domain — not merely engineering — can constitute ethically relevant character information that must be disclosed in employment contexts, because professional integrity is not siloed by discipline.
- Relying on narrow, literal interpretations of disclosure questions to justify omission is ethically insufficient; the spirit and purpose of such questions demand candor that meets the reasonable expectations of a prospective employer.