GeoClear is real-time operational evidence record infrastructure for machine-driven systems. Flood & Census Evidence Record Profile is the reference implementation of the platform applied to mortgage, insurance, and secondary-market review workflows. The same evidence record substrate powers the Location and Decision evidence record profiles.
The platform underneath is decision-domain-agnostic; this page documents what the platform looks like when applied to flood + census + audit-heavy workflows. See Evidence Record Engine for the platform.
What the operational evidence record captures
The operational evidence record captures the fields a mortgage QC reviewer is already reading off the LOS:
- flood_zone
- NFIP-aligned (X / AE / VE / A / etc.)
- flood_sfha
- Special Flood Hazard Area boolean
- flood_base_elevation_ft
- Base flood elevation (NAVD88) when zone is AE/VE
- census_tract
- HMDA LAR-formatted (11-digit GEOID)
- county_fips
- 5-digit county FIPS code
- cra_eligible_tract
- CRA mapping boolean
- risk_score.composite
- Climate-weighted composite score
- full_address
- USPS-canonical (no abbreviation drift)
- lat / lon
- Rooftop-precision coordinates
The record is bound to these fields at decision time. Change one byte, flip a flood-zone code, alter a census tract, and the verification fails. The offline verifier demonstrates this with a tamper test.
Why mortgage teams buy this
- Move first-pass flood and census review into a verifiable evidence bundle.
- Embed the bundle in the loan file alongside the LE/CD, the appraisal, and the title commitment, same workflow, additive artifact.
- Secondary-market reviewer 4 years later asks “what flood zone did the lender rely on?” The bundle answers in 30 seconds, offline, no vendor support ticket.
Sample bundle
Sister evidence record profiles
Flood & Census is one of several evidence record profiles. Each is a reference implementation of the platform applied to a specific decision domain:
Procurement trust anchors
- Operational evidence record issuance happens behind the trust boundary; substrate detail is NDA-only.
- Operational evidence records are retained by the customer in their own substrate; GeoClear does not require continued operation for verification.
- Verification material traces to a stable, customer-verifiable trust anchor.
- SOC 2 Type I in progress.
- Designed to support QC, audit, secondary-market review, and evidence preservation for workflows that use HMDA / NFIP-aligned fields.
What this verifies, and what it doesn’t
What this verifies
- GeoClear issued this operational evidence record at the timestamp inside it.
- The recorded payload has not been mutated since issuance.
- The verification material traces to a stable, customer-verifiable trust anchor.
- The customer can re-verify the record later without contacting GeoClear servers.
What this does not verify
- That every upstream dataset was perfect.
- Full HMDA / NFIP / CRA regulatory compliance.
- That the loan-level decision was risk-free.
- That the physical world matched the recorded values.
Underneath this profile: the Evidence Record Engine platform + Operational Evidence Records. Industry surface: /solutions/mortgage-and-fintech. Compliance brief: /compliance.