Engineer A Verbal-Only Disclosure Insufficiency Obligation Instance
O · Obligation
Individual
http://proethica.org/ontology/case/83#Engineer_A_Verbal-Only_Disclosure_Insufficiency_Obligation_Instance
Properties
Instance of
Verbal-OnlyDisclosureInsufficiencyforPublicAuthorityReportObligation
http://proethica.org/ontology/intermediate#Verbal-OnlyDisclosureInsufficiencyforPublicAuthorityReportObligation
Case context
Engineer A verbally mentioned the threatened species concern to the developer client in subsequent discussions but treated that verbal mention as sufficient, omitting the finding from the written report submitted to the public authority that was relying on the report for its regulatory decision.
Compliance status
unmet
Confidence
0.92
Importance
high
Obligated party
Engineer A (principal, environmental engineering firm)
Obligation statement
Engineer A was obligated to recognize that verbally mentioning the threatened species concern to the developer client did not satisfy the obligation to include that finding in the written report submitted to the public authority, and to ensure the written report reflected all material findings communicated verbally to the client.
Temporal scope
At the time of preparing and submitting the written report to the public authority, following verbal discussions with the developer client
Relationships
defeasibleUnder
Verbal-Only Threatened Species Advisory Without Written Record
derivedFromPrinciple
Written Report Completeness Obligation Applied to Threatened Species Finding
Source Evidence
Source text
In subsequent discussions with the developer client, Engineer A verbally mentions the concern, but Engineer A does not include the information in a written report that will be submitted to a public authority that is considering the developer's proposal
Text references
In subsequent discussions with the developer client, Engineer A verbally mentions the concern, but Engineer A does not include the information in a written report that will be submitted to a public authority that is considering the developer's proposal
TTL
@prefix case83: <http://proethica.org/ontology/case/83#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix proeth: <http://proethica.org/ontology/intermediate#> .
@prefix proeth-core: <http://proethica.org/ontology/core#> .
@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#> .
case83:Engineer_A_Verbal-Only_Disclosure_Insufficiency_Obligation_Instance a proeth:Verbal-OnlyDisclosureInsufficiencyforPublicAuthorityReportObligation,
owl:NamedIndividual ;
rdfs:label "Engineer A Verbal-Only Disclosure Insufficiency Obligation Instance" ;
proeth-core:defeasibleUnder case83:Verbal-Only_Threatened_Species_Advisory_Without_Written_Record ;
proeth:casecontext "Engineer A verbally mentioned the threatened species concern to the developer client in subsequent discussions but treated that verbal mention as sufficient, omitting the finding from the written report submitted to the public authority that was relying on the report for its regulatory decision." ;
proeth:compliancestatus "unmet" ;
proeth:conceptCategory "Obligation" ;
proeth:confidence "0.92" ;
proeth:derivedFromPrinciple case83:Written_Report_Completeness_Obligation_Applied_to_Threatened_Species_Finding ;
proeth:discoveredincase "83" ;
proeth:discoveredinpass "2" ;
proeth:discoveredinsection "facts" ;
proeth:firstdiscoveredat "2026-02-27T18:59:29.260448+00:00" ;
proeth:firstdiscoveredincase "83" ;
proeth:generatedattime "2026-02-27T18:59:29.260448+00:00" ;
proeth:importance "high" ;
proeth:obligatedparty "Engineer A (principal, environmental engineering firm)" ;
proeth:obligationclass "Verbal-Only Disclosure Insufficiency for Public Authority Report Obligation" ;
proeth:obligationstatement "Engineer A was obligated to recognize that verbally mentioning the threatened species concern to the developer client did not satisfy the obligation to include that finding in the written report submitted to the public authority, and to ensure the written report reflected all material findings communicated verbally to the client." ;
proeth:sourcetext "In subsequent discussions with the developer client, Engineer A verbally mentions the concern, but Engineer A does not include the information in a written report that will be submitted to a public authority that is considering the developer's proposal" ;
proeth:temporalscope "At the time of preparing and submitting the written report to the public authority, following verbal discussions with the developer client" ;
proeth:textreferences "In subsequent discussions with the developer client, Engineer A verbally mentions the concern, but Engineer A does not include the information in a written report that will be submitted to a public authority that is considering the developer's proposal" ;
proeth:wasattributedto "Case 83 Extraction" ;
prov:generatedAtTime "2026-02-27T19:15:08.298508"^^xsd:dateTime ;
prov:wasGeneratedBy "ProEthica Case 83 Extraction" .
Metadata
Extraction details
Discovered in case
83
Discovered in pass
2
Discovered in section
facts
First discovered
2026-02-27T18:59:29.260448+00:00
First case
83
Generated
2026-02-27T18:59:29.260448+00:00
Attributed to
Case 83 Extraction
Generated
2026-02-27T19:15:08.298508
Generated by
ProEthica Case 83 Extraction