Mortgage QC | Sample Evidence Bundle

The operational evidence record your QC reviewer drops in next to the loan file. When a secondary-market reviewer asks four years from now what flood determination the lender relied on, this answers, without a vendor support ticket.

Why mortgage teams care

A flood-zone determination + census-tract assignment + risk score sit at the center of every mortgage origination decision. They're already in your loan-origination system. What's typically not in your loan-origination system is a tamper-evident, customer-held verification of exactly what those values were on the day you decided, verifiable years later, independent of the data vendor's continued operation.

An Evidence Bundle is that evidence. Embed it in the loan file alongside the LE/CD, the appraisal, and the title commitment. When a secondary-market reviewer four years from now asks what flood determination the lender relied on, you don't show them a screenshot. You hand them a 23 KB ZIP that re-verifies green in any modern browser.

Field shape

The bundle's verdict carries 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
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 (flood + wildfire + storm + seismic + drought)
full_address: USPS-canonical (no abbreviation drift)
lat / lon: Rooftop-precision coordinates (IANA-timezoned)

The operational evidence 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 bundle's offline verifier demonstrates this with a tamper test.

What this bundle is

The TX-0001 sample is a customer-held evidence package generated against the live /api/demo endpoint for verification testing. The bundle verifies independently using retained verification material, no GeoClear server is required for the verification result.

Open the browser verifier. Drag the bundle in. Watch the verification turn green. Try the tamper test, flip a byte, watch the verification reject it.

What this verifies, and what it doesn't

What this verifies

✓ GeoClear issued this operational evidence record at the timestamp recorded inside it.
✓ The retained evidence matches the record.
✓ The verification material active at issuance time validates.
✓ The record was not modified after issuance.

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.

How a mortgage QC team typically uses this

At origination, the LOS calls GeoClear and retains the response along with the operational evidence record returned in the response headers.
The QC pipeline packages the record + retained evidence + verification material into a bundle ZIP using our public verifier (see developer docs for integration detail).
The bundle is filed alongside the loan documents in the existing document-management system.
If any future review, QC sample, secondary-market diligence, regulator inquiry, asks "what flood determination did the lender rely on?", the file's bundle answers in 30 seconds, offline.

Mortgage QC: the customer-held operational evidence record your loan file holds.