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
Coordinate a disaster response from one event record
Record a portfolio event once. LendEasy identifies the affected population, opens a case for each borrower, and checks the proposed relief using each borrower’s facts and restrictions before anything executes.
One event, individual decisions
Human
Hurricane hits — event declared once
System
A case opens for each affected borrower
Compliance Gate
Each borrower is evaluated individually
Ledger
Individual results are recorded
Every borrower gets an individual decision; full walkthrough below
The scenario
From declaration to per-borrower results
Follow a portfolio event through population selection, individual cases, policy decisions, assigned work, and recorded results.
- Human
A hurricane makes landfall — a portfolio event is declared
A manager records the event, its basis, and the criteria that define who is affected.
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
A case opens for each affected borrower
Each borrower receives an individual case under the portfolio event, with the account facts available at the time.
Evidence: One subcase per borrower, linked to the parent event.
- Human
Portfolio action proposed: pause outreach, offer hardship relief
A manager proposes the action for the affected population. Nothing executes until each borrower is evaluated.
Evidence: The proposed action, its terms, and its proposer.
- Compliance Gate
Each borrower receives a separate policy decision
The gate evaluates the proposed action for each borrower, then separates the population by outcome.
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 and the reason is recorded
Evidence: An individual gate decision per borrower — every allow, approval, and block, with the rules consulted.
- System
Work routes to the right queues
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
Results tracked for each borrower
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, linked event record, exportable for examiners.
Per-borrower evaluation
One portfolio action, individual decisions
A portfolio-wide relief action still has to respect each borrower's restrictions, consent, jurisdiction, and account state. LendEasy evaluates those facts before anything executes.
LendEasy evaluates each borrower’s restrictions, consent, jurisdiction, and account state. The result is allowed, human approval required, or blocked, with the reason recorded for each person.
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 on the borrower's event case.
Beyond disasters
Coordinate changes across many accounts
Use the same workflow for fee remediation, corrected communications, or a regulatory review: define the population, propose the action, evaluate each borrower, assign the work, and record the results.
Recall campaigns
When a disclosure or message needs correction, define the affected population, evaluate the resend for each borrower, and track each result.
Regulatory sweeps
When a new rule or exam finding affects many accounts, open a case for each borrower, route the work, and keep an individual record of the result.
Manager visibility
Track the full event in one place
See population size, decisions, outstanding work, and results, then open any individual borrower record when more detail is needed.
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.
Open any borrower record
Move from the portfolio view to one borrower's decision, offer, response, and audit history.
FAQ
Portfolio events, answered
A portfolio action can be proposed once, but individual borrowers may have different restrictions, consent, jurisdictions, or account states. Evaluating each borrower applies the relief only where the configured rules allow it and records exclusions with their reasons.
Walk through a portfolio event
Choose a storm, remediation, or regulatory-sweep scenario. We will build the population, evaluate the proposed action per borrower, and trace the resulting work and evidence.