Post-Client-Refusal Escalation Assessment Obligation Invoked by BER Discussion Section
P · Principle
Individual
http://proethica.org/ontology/case/88#Post-Client-Refusal_Escalation_Assessment_Obligation_Invoked_by_BER_Discussion_Section
Properties
Instance of
Post-Client-RefusalEscalationAssessmentObligation
http://proethica.org/ontology/intermediate#Post-Client-RefusalEscalationAssessmentObligation
Applied to
Client B's refusal to fund specialized hydrologic analysis
Decision whether to submit engineering report to regulatory agencies
Balancing with
Client Loyalty
Faithful Agent Obligation Within Ethical Limits
Concrete expression
The BER holds that if Client B remains unconvinced after Engineer A's advocacy, Engineer A must propose submission of an engineering report to regulatory agencies for public consideration — and if Client B refuses even that intermediate escalation step, Engineer A must withdraw from the project.
Confidence
0.96
Importance
high
Interpretation
In this context, the post-refusal escalation principle generates a two-stage escalation obligation: first, propose regulatory report submission; second, withdraw if client refuses both analysis and disclosure. The client's refusal does not discharge Engineer A's independent public protection obligation.
Invoked by
Engineer A Climate Change Impact Evaluating Infrastructure Engineer
Tension resolution
Post-refusal escalation obligation overrides client preference for silence; Engineer A must escalate to regulatory disclosure or withdraw, rather than treating client refusal as a complete discharge of professional obligation.
Source Evidence
Source text
If Client B remains unconvinced, Engineer A should propose to Client B that engineer a provides the potential concern that may necessitate more detailed evaluation in an engineering report for consideration by regulatory agencies and the public. Failing agreement by Client B to either of these courses of action the BER believes that Engineer A should withdraw from the project.
Text references
Failing agreement by Client B to either of these courses of action the BER believes that Engineer A should withdraw from the project.
If Client B remains unconvinced, Engineer A should propose to Client B that engineer a provides the potential concern that may necessitate more detailed evaluation in an engineering report for consideration by regulatory agencies and the public.
The BER concluded that Engineer A should continue to attempt to convince the owner of the potential for damage to future residents and the public, and, failing agreement on Engineer A's proposed design standard, Engineer A should withdraw from the project.
TTL
@prefix case88: <http://proethica.org/ontology/case/88#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix proeth: <http://proethica.org/ontology/intermediate#> .
@prefix prov: <http://www.w3.org/ns/prov#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
case88:Post-Client-Refusal_Escalation_Assessment_Obligation_Invoked_by_BER_Discussion_Section a proeth:Post-Client-RefusalEscalationAssessmentObligation,
owl:NamedIndividual ;
rdfs:label "Post-Client-Refusal Escalation Assessment Obligation Invoked by BER Discussion Section" ;
proeth:appliedto "Client B's refusal to fund specialized hydrologic analysis",
"Decision whether to submit engineering report to regulatory agencies" ;
proeth:balancingwith "Client Loyalty",
"Faithful Agent Obligation Within Ethical Limits" ;
proeth:conceptCategory "Principle" ;
proeth:concreteexpression "The BER holds that if Client B remains unconvinced after Engineer A's advocacy, Engineer A must propose submission of an engineering report to regulatory agencies for public consideration — and if Client B refuses even that intermediate escalation step, Engineer A must withdraw from the project." ;
proeth:confidence "0.96" ;
proeth:discoveredincase "88" ;
proeth:discoveredinpass "2" ;
proeth:discoveredinsection "discussion" ;
proeth:firstdiscoveredat "2026-02-27T14:20:08.457238+00:00" ;
proeth:firstdiscoveredincase "88" ;
proeth:generatedattime "2026-02-27T14:20:08.457238+00:00" ;
proeth:importance "high" ;
proeth:interpretation "In this context, the post-refusal escalation principle generates a two-stage escalation obligation: first, propose regulatory report submission; second, withdraw if client refuses both analysis and disclosure. The client's refusal does not discharge Engineer A's independent public protection obligation." ;
proeth:invokedby "Engineer A Climate Change Impact Evaluating Infrastructure Engineer" ;
proeth:principleclass "Post-Client-Refusal Escalation Assessment Obligation" ;
proeth:sourcetext "If Client B remains unconvinced, Engineer A should propose to Client B that engineer a provides the potential concern that may necessitate more detailed evaluation in an engineering report for consideration by regulatory agencies and the public. Failing agreement by Client B to either of these courses of action the BER believes that Engineer A should withdraw from the project." ;
proeth:tensionresolution "Post-refusal escalation obligation overrides client preference for silence; Engineer A must escalate to regulatory disclosure or withdraw, rather than treating client refusal as a complete discharge of professional obligation." ;
proeth:textreferences "Failing agreement by Client B to either of these courses of action the BER believes that Engineer A should withdraw from the project.",
"If Client B remains unconvinced, Engineer A should propose to Client B that engineer a provides the potential concern that may necessitate more detailed evaluation in an engineering report for consideration by regulatory agencies and the public.",
"The BER concluded that Engineer A should continue to attempt to convince the owner of the potential for damage to future residents and the public, and, failing agreement on Engineer A's proposed design standard, Engineer A should withdraw from the project." ;
proeth:wasattributedto "Case 88 Extraction" ;
prov:generatedAtTime "2026-02-28T10:32:26.863212"^^xsd:dateTime ;
prov:wasGeneratedBy "ProEthica Case 88 Extraction" .
Metadata
Extraction details
Discovered in case
88
Discovered in pass
2
Discovered in section
discussion
First discovered
2026-02-27T14:20:08.457238+00:00
First case
88
Generated
2026-02-27T14:20:08.457238+00:00
Attributed to
Case 88 Extraction
Generated
2026-02-28T10:32:26.863212
Generated by
ProEthica Case 88 Extraction