Fee remediation
A fee was misapplied across part of the portfolio. Build the affected population from ledger facts, propose the remediation once, evaluate per borrower, and track every correction to completion.
Solutions · Disaster response & portfolio events
When a hurricane hits, answer in hours — not weeks
Declare a portfolio event once. The platform builds the impact population, fans out a subcase per borrower, and runs your relief action through per-borrower compliance evaluation — so help moves at portfolio speed without a single blanket blast.
One event, individual judgment
Human
Hurricane hits — event declared once
System
Per-borrower subcases fan out
Compliance Gate
Every borrower evaluated individually
Ledger
Per-borrower results, exam-ready
No blanket blasts — every borrower gets their own decision; full walkthrough below
The scenario
From declaration to per-borrower results
One event, thousands of individual decisions. Watch the gate split the population before anything executes — and notice that the event keeps absorbing new borrowers as the zone grows.
- Human
A hurricane makes landfall — a portfolio event is declared
A manager declares the event once, with a name, a basis, and the criteria that define who is affected. Everything that follows hangs off this one declaration.
Evidence: The declaration: who declared it, when, and on what basis.
- System
Impact population built from geography and portfolio criteria
Affected counties, ZIP codes, product types, delinquency status — the platform resolves the criteria into a concrete list of borrowers, not a guess.
Evidence: The criteria and the exact resulting population, versioned.
- System
Per-borrower subcases fan out
Every affected borrower gets their own subcase under the event, each with its own context snapshot — so individual situations are handled individually, at portfolio scale.
Evidence: One subcase per borrower, linked to the parent event.
- Human
Mass action proposed: pause outreach, offer hardship relief
The action is proposed once, against the whole population. Proposing is cheap — nothing has executed yet.
Evidence: The proposed action, its terms, and its proposer.
- Compliance Gate
Per-borrower compliance evaluation — the split happens here
There is no blanket blast. The gate evaluates the action against each borrower individually, and the population splits.
Allowed
- The action proceeds for these borrowers
- Outreach pauses; the hardship offer goes out
Approval required
- Edge cases route to a human before anything executes
- Approved or declined per borrower, with reasons
Blocked
- Bankruptcy stay, cease-communications, other restrictions
- These borrowers are excluded — automatically, provably
Evidence: An individual gate decision per borrower — every allow, approval, and block, with the rules consulted.
- System
Instruction tasks distribute the work
Approvals, follow-ups, and exceptions become tasks routed to workers through the same queues humans and AI agents already share.
Evidence: Each task, its assignee, and its disposition.
- System
The disaster zone grows — the population grows with it
New counties added to the declaration flow in as incremental additions. New borrowers get subcases and the same per-borrower evaluation — no re-running the whole event, no double-sending to those already handled.
Evidence: Each population increment and the evaluations it triggered.
- Ledger
Full per-borrower result tracking
Who was offered relief, who accepted, who was excluded and why — the event resolves into per-borrower results, not a campaign-level summary.
Evidence: The complete event record, hash-chained and exportable for examiners.
No blanket blasts
Mass action, individual judgment
The fastest way to turn a goodwill gesture into a violation is to send it to everyone. Somewhere in your impact population is a borrower under a bankruptcy stay, one who told you to stop calling, one whose state regulates the very message you are about to send.
LendEasy proposes once and decides per borrower. The gate evaluates each individual against the action — restrictions, consent, jurisdiction — and the population splits into allowed, approval-required, and blocked. The blocked borrowers are not a failure of the campaign; they are the proof it was run lawfully.
One proposed mass action · 60 individual gate decisions
48 allowed — action proceeds7 need approval first5 blocked — stay, cease-comms…
Illustrative population. Every decision — including each block — is recorded per borrower in the event's evidence graph.
Beyond disasters
Any time you must touch many accounts, carefully
The portfolio-event machinery is general: a defined population, a proposed action, per-borrower gates, distributed work, and per-borrower results.
Recall campaigns
A disclosure or message needs to be corrected and re-sent. Same machinery: population from criteria, per-borrower gates so the correction itself cannot create a violation, full result tracking.
Regulatory sweeps
A new rule or an exam finding requires touching every affected account. Declare it as an event, fan out subcases, distribute the work, and hand the examiner the per-borrower record.
Manager visibility
Run the event like an operation, not an email thread
During a disaster, leadership asks one question on repeat: where are we? The event view answers it continuously, from portfolio roll-up to a single borrower's record.
The event at a glance
Population size, evaluation split, tasks outstanding, results so far — one live view of the whole event instead of a status meeting.
Work you can steer
Instruction tasks show queue depth and progress by team. Rebalance, reprioritize, or add reviewers while the event runs — without losing the thread.
Per-borrower drill-down
From the portfolio view to any single borrower's subcase in two clicks: their gate decision, their offer, their response, their evidence.
FAQ
Portfolio events, answered
You can propose exactly that — and the platform will still evaluate it per borrower. That is a feature: some borrowers in the population may be under restrictions or in states where the action, or the message announcing it, is constrained. Per-borrower evaluation means the relief goes out fast and none of it creates a new violation.
Run a portfolio event with us, live
Pick a scenario — storm, remediation, sweep. We will declare the event, build the population, and watch the per-borrower gates split it, live with the founding team.