In production with U.S. mortgage servicers
v3 Audit-ready evidence bundle, per portfolio

Mortgage insurance
compliance, automated.

Covera reads every declarations page, flags coverage gaps, lapses, and flood-mandate violations against citation-backed rules, and runs the RESPA force-placement cure workflow end to end — with an audit-ready evidence bundle for every exception.

Representative servicing portfolio · figures vary by book

<60s
Dec pages to exceptions
5,000-loan portfolio scan
4
Regulatory rule families
Flood, adequacy, lapse, escrow
45d
RESPA cure clock
Dual notice + proof of delivery
100%
Cited rules
Every flag traces to a regulation
10
Files per evidence bundle
SHA-256 signed, fully replayable
0.853
Disaster-default AUC
Climate Foresight add-on · 14.8M Freddie loans

What your servicing system doesn't catch

Servicing platforms track escrow and payments, not whether each loan actually carries the coverage its note and the regulators require. The gaps that trigger force-placement errors, RESPA findings, and investor repurchase demands sit in declarations pages no one has read. Covera reads them.

Flood
Mandatory-purchase violations

Loans secured by property in an SFHA without conforming flood coverage. A documented violation of 42 U.S.C. §4012a with direct civil-penalty and repurchase exposure.

Gaps
Inadequate dwelling coverage

Policies whose dwelling limit falls short of replacement cost or the unpaid balance. The uninsured wedge the bank eats after a loss — itemized per loan.

Lapse
Expiring & lapsed policies

Coverage that has lapsed or expires inside the notice window, surfaced before the force-placement clock starts — not after a claim is denied.

Four rule families, every flag cited

Each loan is evaluated against a versioned, investor- and state-scoped rule set. Every finding carries the regulation it enforces and a severity, so a flag is never a black box. Climate Foresight adds a forward-looking exposure layer on top.

Flood mandate

SFHA-secured loans checked for conforming flood coverage and the regulatory minimum limit.

42 U.S.C. §4012a · FEMA NFHL

Coverage adequacy

Dwelling limit tested against replacement cost and unpaid balance, with the NFIP cap applied.

Investor guide · replacement cost

Lapse & expiry

Policies that have lapsed or expire inside the notice window, flagged before the cure clock starts.

Note covenant · notice window

Escrow shortage

Premium escrow tested for shortage and deficiency tolerance ahead of the next disbursement.

RESPA Reg X · escrow analysis
Add-on

Climate Foresight

Forward-looking flood, wildfire, wind, and heat exposure on each property to anticipate where adequacy fails next.

FEMA NRI · USFS WHP · NOAA
Rules are configurable, not hard-coded

Every rule family is a versioned config with its own parameters, severity, and investor/state scope — an NFIP cap here, an adequacy tolerance there, a notice window per state. Compliance edits a rule set, saves a new version, and activates it; the change is logged with who, when, and what. No engineering ticket, and the prior version stays replayable for any exam that reaches back to it.

From declarations page to cured exception

Every loan moves through the same five stations — the exact workflow a compliance team runs by hand today, automated and logged end to end.

01

Intake

Declarations pages are parsed by an AI extractor — carrier, policy number, dwelling limit, deductible, term, flood rider — with a confidence score and a heuristic fallback when a document is messy.

02

Detect

The rule engine evaluates every loan against the active rule set — flood mandate, coverage adequacy, lapse/expiry, escrow shortage — and opens an exception case for each finding, with the citation attached.

03

Notice

RESPA / Reg X borrower notices are generated on the correct schedule and dispatched through a delivery provider that returns a tracking number and proof-of-delivery receipt for the file.

04

Cure

The force-placement cure workflow tracks the 45-day clock, records borrower-supplied evidence, and gates force-placement until the dual-notice requirement is satisfied. Every transition is an immutable event.

05

Evidence

A signed evidence bundle (SHA-256) is produced on demand: findings, notices sent, delivery receipts, cure history, and the exact rule-set version applied. Replayable for any exam.

A human stays in the loop where it counts

Low-confidence extractions and high-severity findings land in a prioritized review queue with an SLA clock, so a person confirms the call before a notice goes out or a policy is force-placed. Everything else flows automatically. The result is the throughput of automation with the defensibility of human sign-off — and a complete event trail either way.

Deliverables

Three artifacts for every portfolio: a per-loan coverage record, a live compliance dashboard, and a signed, audit-ready evidence bundle. When a declarations page can't be read with confidence, the loan routes to review rather than guessing. No coverage value is ever synthesized.

Per-loan coverage record

  • carrier / policy_noparsed
  • dwelling_limit$
  • replacement_cost vs upb$
  • flood_requiredSFHA
  • coverage_gap_$$
  • effective / expirydate
  • findings[]+ citation
  • extraction_confidence0–1
  • priority / sla_due_atqueue
  • cure_statusopen…cured

Compliance dashboard

  • Compliance KPIs: open exceptions & UPB at risk
  • Review queue, prioritized with SLA status
  • Force-placement cure board with the 45-day clock
  • Proof-of-delivery timeline per notice
  • Rule sets: edit, version, and activate in-product
  • Servicing system-of-record sync history
  • Cure-cycle throughput and aging
  • Citation on every finding that fires

Signed evidence bundle

  • Signed bundle with SHA-256 + verify URL
  • Findings register with rule citation per loan
  • Notices sent + proof-of-delivery receipts
  • Force-placement cure history & event trail
  • Exact rule-set version applied (replayable)
  • Dec-page extractions + confidence scores
  • Reviewer sign-off and assignment log
  • RESPA / Reg X & flood-mandate mapping
Representative scan · 4,950 loans

On a servicing portfolio

A residential servicing book of 4,950 loans, scanned against the default rule set. The figures below are illustrative of a first-pass result; your numbers depend on the book and the rule set you activate.

Open exceptions
312
Across all four rule families
UPB at risk
$86M
Unpaid balance behind flagged loans
Flood-mandate gaps
41
SFHA loans without conforming coverage
Scan runtime
<60s
Dec pages parsed to exceptions opened
Exceptions by rule family
  1. Flood mandate (SFHA)41 loans
  2. Coverage adequacy gap128 loans
  3. Lapsed / expiring policy96 loans
  4. Escrow shortage47 loans
Actions taken
  • High-severity findings routed to the review queue
  • First RESPA notice generated for 137 cure cycles
  • Proof-of-delivery receipts captured per notice
  • Signed evidence bundle exported for the next exam

Figures are illustrative of a representative first-pass scan and vary by book and active rule set. Rules are defined in versioned, investor- and state-scoped rule sets. Covera does not synthesize coverage values; declarations pages it cannot read with confidence route to human review.

Implementation

No rip-and-replace. Four steps from your servicing book to a cured, documented exception.

1

Connect the book and the documents

Upload a loan tape and declarations pages, or sync directly from your servicing system of record. Covera handles batch dec-page intake at scale. AES-256 encryption in transit and at rest; data is purged on request.

2

Run the scan

Dec pages are parsed and every loan is evaluated against your active rule set — flood mandate, coverage adequacy, lapse/expiry, escrow shortage. Exceptions open automatically, each with its citation. A 5,000-loan book scans in under a minute.

3

Work the review queue

Low-confidence extractions and high-severity findings surface in a prioritized queue with an SLA clock. Reviewers confirm, assign, and approve in-product. Confirmed exceptions advance to the notice and cure workflow.

4

Cure, then export the evidence bundle

RESPA notices go out with proof of delivery, the 45-day clock runs, and force-placement is gated until the requirements are met. The signed evidence bundle — findings, notices, receipts, cure history, and the rule-set version applied — exports on demand for any exam.

Sources & integrations

Flood determinations and Climate Foresight trace to verified government sources; loan and coverage data flow in from your servicing system of record. No proprietary blends, no opaque third-party indexes.

FEMA Flood Zones
National Flood Hazard Layer
FEMA NRI
National Risk Index
USFS Wildfire
Wildfire Hazard Potential
NOAA Storms
Storm Events Database
FEMA Declarations
Disaster Declarations
FEMA PA Grants
Public Assistance Awards
NFIP Policies
Flood Insurance in Force
HMDA Lending
CFPB Mortgage Data
Census ACS
Housing Cost Burden
Freddie Mac
14.8M Loan Performance
Residual Markets
FL Citizens, CA FAIR, TWIA
NASA / NOAA
Climate Projections & SLR
Live
Servicing SoR
System-of-record sync
Live
Dec-page AI intake
Declarations-page parser
RESPA / Reg X
Force-placement rules

Who it's for

Four roles inside a mortgage servicer or bank. No new data-science team required.

Insurance compliance

A single queue of coverage exceptions ranked by severity and SLA, each tied to the regulation it enforces. Replaces spreadsheet tracking of dec pages and notice deadlines.

Default & loss mitigation

The force-placement cure workflow with the 45-day clock, dual-notice gating, and proof of delivery — so policies are force-placed correctly, on time, and never in violation of RESPA.

Servicing operations

Dec-page intake at scale synced from the system of record, with extraction confidence and a review queue. Coverage status stays current without manual data entry.

Audit & exam

A signed evidence bundle covering findings, notices sent, delivery receipts, cure history, and the exact rule-set version applied — replayable for any exam or investor review.

Frequently asked questions

Direct answers to the questions raised by servicing, compliance, and audit teams in initial calls.

Doesn’t our servicing system already track insurance?
Servicing platforms store a policy field; they don’t read the declarations page or judge whether the coverage actually satisfies the flood mandate, replacement-cost adequacy, or your investor’s guide. Covera parses the dec page, applies citation-backed rules, and runs the cure workflow. It sits on top of your system of record — syncing loan data in and writing exceptions and evidence back — not in front of it.
How is this different from an insurance-tracking vendor?
Traditional trackers are an outsourced call center that chases paper and force-places aggressively, with little transparency into why. Covera is software you control: configurable, citation-backed rules; an auditable cure workflow with proof of delivery; and a signed evidence bundle for every exception. You keep the borrower relationship and the audit trail instead of renting them.
How accurate is the dec-page parsing, and what if it’s wrong?
Every extraction carries a confidence score, with a heuristic fallback when a document is poor quality. Anything below threshold — or any high-severity finding — routes to the review queue for human sign-off before a notice goes out. Covera never fabricates a coverage value; an unreadable field is flagged for review, not guessed.
Is every exception auditable line-by-line?
Yes. Each exception records the rule that fired and its citation, the parsed dec-page values and confidence, the reviewer who signed off, every notice sent with its delivery receipt, and the full cure event trail. The evidence bundle pins the exact rule-set version applied, with a SHA-256 signature, so any decision is replayable years later.
How long from loan book to open exceptions?
Rule evaluation on a 5,000-loan book runs in under a minute once dec pages are parsed. Dec-page parsing is the longer step and scales with batch size; the intake queue processes documents in parallel and surfaces results as they complete, so the review queue starts filling immediately rather than waiting for the whole batch.
Can we configure the rules to our investors and states?
Yes — that’s the core of it. Rule sets are versioned and scoped by investor and state, with per-rule parameters (NFIP cap, adequacy tolerance, notice window) and severity overrides. Compliance edits a rule set, saves a new version, and activates it; the change is logged, and prior versions stay replayable for any exam that reaches back to them.
Does the force-placement workflow meet RESPA / Reg X?
The cure workflow encodes the Reg X sequence: a first notice, a reminder at least 30 days later, a 45-day cure window, and a hard gate that blocks force-placement until the dual-notice requirement is satisfied and proof of delivery is on file. Each step is an immutable event, and refunds on overlap are tracked — so the file tells the examiner exactly what happened and when.
What happens when a declarations page is missing entirely?
A missing dec page is itself an exception — the loan is flagged as “no evidence of coverage” and routed for outreach, not assumed compliant. Covera never fills the gap with a synthesized policy or a peer proxy. The audit trail records exactly what was on file and what was requested.

Request a portfolio assessment

Pilot engagements are complimentary: send a sample of your book and declarations pages and we return a scored exception report with an audit-ready evidence bundle. Initial review takes approximately forty-five minutes.

Or email us directly at james@clima.solutions